Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011549Dwarf FortressMiscellaneous Crashespublic2020-05-25 20:402021-01-22 15:23
Reporterantielectron 
Assigned Tolethosor 
PriorityhighSeveritycrashReproducibilityalways
StatusresolvedResolutionfixed 
PlatformWindowsOSWindows 10 ProOS Version1909
Product Version0.47.04 
Target VersionFixed in Version0.47.05 
Summary0011549: Crash when off-site werecreature gives birth
DescriptionGame crashes after date: 251-3-23

This was my first dwarf fortress run ever :( Any chance I can continue it?
Steps To ReproduceLoad the save game below and let the time get to 251-3-23 (take a couple of minutes).

http://dffd.bay12games.com/file.php?id=15092 [^]
Additional InformationI tried varying what I did in-game to get around the crash, but no good. Also tried disbanding my squads and setting my pyLNP visitor cap to zero - because I saw in forums that that has helped other people, but that attempts didn't work for me.

More saves:
https://dffd.bay12games.com/file.php?id=15114 [^] (0011560, 0.47.04)
https://dffd.bay12games.com/file.php?id=15134 [^] (0011571, 0.47.04)
TagsSave Included, werebeast
Relationships
has duplicate 0011560resolved lethosor Consistent crash, unknown reason 
has duplicate 0011571resolved lethosor Game crashes seconds in 
has duplicate 0011573resolved lethosor game crashes shortly after load 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2020-05-25 20:40antielectronNew Issue
2020-05-26 00:04PatrikLundellNote Added: 0040568
2020-07-03 08:57QuietustNote Added: 0040609
2020-07-03 08:58QuietustNote Edited: 0040609bug_revision_view_page.php?bugnote_id=0040609#r16512
2020-07-03 08:58QuietustNote Edited: 0040609bug_revision_view_page.php?bugnote_id=0040609#r16513
2020-07-03 08:59lethosorRelationship addedhas duplicate 0011560
2020-07-03 08:59lethosorRelationship addedhas duplicate 0011571
2020-07-03 09:01lethosorAdditional Information Updatedbug_revision_view_page.php?rev_id=16516#r16516
2020-07-03 09:03lethosorNote Added: 0040611
2020-07-03 09:03lethosorAssigned To => lethosor
2020-07-03 09:03lethosorStatusnew => acknowledged
2020-07-03 09:03lethosorTag Attached: Save Included
2020-07-03 09:13lethosorTag Attached: werebeast
2020-07-03 09:13lethosorSummaryReliable Crash => Crash when off-site werecreature gives birth
2020-07-03 09:14QuietustNote Added: 0040612
2020-07-03 09:17lethosorStatusacknowledged => confirmed
2020-07-03 09:18lethosorNote Edited: 0040611bug_revision_view_page.php?bugnote_id=0040611#r16518
2020-07-08 03:26PatrikLundellNote Added: 0040618
2020-08-08 10:54lethosorRelationship addedhas duplicate 0011573
2020-11-16 11:42psychowicoNote Added: 0040794
2021-01-21 19:25lethosorSticky IssueNo => Yes
2021-01-22 15:23Toady OneStatusconfirmed => resolved
2021-01-22 15:23Toady OneFixed in Version => Next Version
2021-01-22 15:23Toady OneResolutionopen => fixed

Notes
(0040568)
PatrikLundell   
2020-05-26 00:04   
Repeated the crash on my Win64 system. I found no zero size creatures or equipment corruption.
Hooking up a debugger to DF shows the crash is caused by an access violation trying to read location 0xFFFFFFFFFFFFFFFF.
(0040609)
Quietust   
2020-07-03 08:57   
(edited on: 2020-07-03 08:58)
This appears to be the exact same crash seen in 0011571 - a Human named "Olo Lapaslibtu" (unit 5349, histfig 40304) is giving birth to a child while transformed into a Wereantelope.
(0040611)
lethosor   
2020-07-03 09:03   
(edited on: 2020-07-03 09:18)
Since this is the oldest of the three instances of this issue identified (so far), I'm planning on consolidating any other discovered duplicates here (even if they're older).

I was also able to reproduce (on Linux, 0.47.04 64-bit)
(0040612)
Quietust   
2020-07-03 09:14   
The problem seems to be that the units are trying to give birth to MALE offspring (with caste id == 1), even though werecreatures only have a single DEFAULT caste (with caste id == 0).
(0040618)
PatrikLundell   
2020-07-08 03:26   
Changing the death time of the historical figure to the current time (i.e. shortly before the crash would occur) with DFHack allows the save to proceed beyond the crash point, but the side effects of the unrecorded death of the HF are unknown.

(As 0011571 has been resolved, I can't add a comment to it. For anyone else looking at the corresponding save, the histfig id given by Quietust has the last two digits swapped, it should have been 78836.)
(0040794)
psychowico   
2020-11-16 11:42   
I have crash that looks similar. How I could confirm this?

Is there a way to check if it is the case by using dfhack lua interface?