View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0007230Dwarf FortressAdventure Mode -- Character Creationpublic2014-07-13 14:302014-07-13 23:51
Reporterdree12 Assigned Touser11 
PrioritynormalSeveritycrashReproducibilityalways
Status resolvedResolutionduplicate 
PlatformLinux SDL x86-64OSUbuntuOS Version14.04
Product Version0.40.03 
Summary0007230: Crash when creating new adventurer
DescriptionIn the world below, when creating a new adventurer (Demigod Locally Important Dwarf of Kib Lûk with all points poured into Strength, Agility, Toughness, and Hammerdwarf), there is a crash.

Terminal reads:


terminate called after throwing an instance of 'std::bad_alloc'
  what(): std::bad_alloc
Aborted (core dumped)


The error log is completely blank. This bug reproduces 100% of the time or close to it. I have not tried with different skill and attribute assignments, but I doubt they matter.

This is a newly-minted world; nothing has been done to it yet. Before the crash there is a short hang. This also does not seem to be a calendar problem as the calendar has already run by the time the adventurer creation screen appears.

Save file: http://dffd.wimbli.com/file.php?id=8948
Steps To Reproduce

  • Play "Adventurer" mode.

  • Select a Demigod Dwarf of Kib Lûk.

  • Maximize Strength, Agility, Toughness, and Hammerdwarf.

  • Select "Locally Important".

  • Continue and notice that Dwarf Fortress hangs and eventually crashes.

TagsCLOSE THIS

Relationships

duplicate of 0005283 resolvedToady One Crash upon accepting/saving a generated world when old-version saves are present 

Activities

yamamushi

2014-07-13 16:16

reporter   ~0026228

Can confirm this is happening with this save file on OSX Mavericks as well, I've pasted a crash log here:

http://pastebin.com/G0ehDtFX

dree12

2014-07-13 16:52

reporter   ~0026233

Last edited: 2014-07-13 16:54

 I've figured this out I think, and it's probably not a bug. I overwrote my 0.40.02 installation with 0.40.03 and forgot to delete "region1". When I generated a new region, it must have added the new region's files but not removed the old region's files. Due to my negligence, the region is corrupted.

I am well aware that it is not a good idea to rewrite old installations of DF and I let my laziness get the better of me this time.

I confirmed this hypothesis by looking at the "last modified" dates, some of which were many days before this region was generated. I apologize for the mistaken bug report. This can safely be closed now.

dree12

2014-07-13 17:04

reporter   ~0026234

Sure enough, the save works perfectly after all old files are removed. This was a false alarm; please close this report.

user11

2014-07-13 17:14

  ~0026237

Thanks for the follow-up, dree12. yamamushi, if this doesn't explain your situation, please let us know or see if there's another report that covers it.

Issue History

Date Modified Username Field Change
2014-07-13 14:30 dree12 New Issue
2014-07-13 16:16 yamamushi Note Added: 0026228
2014-07-13 16:52 dree12 Note Added: 0026233
2014-07-13 16:53 dree12 Note Edited: 0026233
2014-07-13 16:53 dree12 Tag Attached: CLOSE THIS
2014-07-13 16:54 dree12 Note Edited: 0026233
2014-07-13 17:04 dree12 Note Added: 0026234
2014-07-13 17:14 user11 Note Added: 0026237
2014-07-13 17:14 user11 Status new => resolved
2014-07-13 17:14 user11 Resolution open => no change required
2014-07-13 17:14 user11 Assigned To => user11
2014-07-13 23:50 user6 Resolution no change required => duplicate
2014-07-13 23:51 user6 Relationship added duplicate of 0005283