Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011030Dwarf FortressTechnical -- Saving/Loadingpublic2019-02-15 19:152020-02-13 20:49
ReporterTack 
Assigned ToToady One 
PrioritynormalSeveritycrashReproducibilityalways
StatusresolvedResolutionfixed 
PlatformPC - WindowsOSWin 10 ProOS Version-
Product Version0.44.12 
Target VersionFixed in Version0.47.01 
Summary0011030: Crash on save, does not save
DescriptionGame crashes when saving, at the point where 'Saving Fortress Information' is reached.
Steps To ReproduceManual save.
Additional InformationNo major changes in fortress management. Recently raided a large neighbouring stronghold.
Tags0.44.12, crash, save
Relationships
related to 0010939resolved Loci segfault on "Saving fortress information" when trying to save, reproducible via savestate 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2019-02-15 19:15TackNew Issue
2019-02-15 19:16TackTag Attached: 0.44.12
2019-02-15 19:16TackTag Attached: crash
2019-02-15 19:16TackTag Attached: save
2019-02-15 19:16TackIssue Monitored: Tack
2019-02-15 19:16TackIssue End Monitor: Tack
2019-02-15 19:24TackNote Added: 0039218
2019-02-16 08:49LociRelationship addedchild of 0010939
2019-02-16 08:58LociNote Added: 0039219
2019-02-16 08:58LociAssigned To => Loci
2019-02-16 08:58LociStatusnew => confirmed
2020-01-29 00:38Toady OneRelationship replacedrelated to 0010939
2020-02-13 20:49Toady OneNote Added: 0040052
2020-02-13 20:49Toady OneStatusconfirmed => resolved
2020-02-13 20:49Toady OneFixed in Version => 0.47.01
2020-02-13 20:49Toady OneResolutionopen => fixed
2020-02-13 20:49Toady OneAssigned ToLoci => Toady One

Notes
(0039218)
Tack   
2019-02-15 19:24   
Possible links - 0006463, 0001371

Save game: http://dffd.bay12games.com/file.php?id=14251 [^]

Running DF Vanilla, no hack, no therapist.
(0039219)
Loci   
2019-02-16 08:58   
Crash reproduced; probably 0010939, but I'll leave this report open until we confirm a fix.
(0040052)
Toady One   
2020-02-13 20:49   
This works for me now, so I assume it was one of the two visitor crashes that acted like this before 47.01.