|Anonymous | Login | Signup for a new account||2019-04-25 21:32 PDT|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0011082||Dwarf Fortress||Technical -- Saving/Loading||public||2019-04-13 01:15||2019-04-14 23:02|
|Target Version||Fixed in Version|
|Summary||0011082: Saving always crashes at "Saving fortress information"|
|Description||Every time I try to save, to shut down the PC, the saving process stops at "Saving fortress information" and I get thrown to the Desktop. |
|Steps To Reproduce||http://dffd.bay12games.com/file.php?id=14334 [^]|
Just try to save the game
|Additional Information||-There is no Error Message I noticed and the errorlog.txt didn't helped me either. |
-The map is bigger than the default Option but I don't remember how big it was.
-You can just play fine wihtout any crashes, just saving is impossible.
-Up until this point I could just play fine without any crashes.
-The Fortress ist around 7~8(in game)Years old at the time you load the file.
-1050 years of History were generated.
-I restarted the System many times without any difference.
-I use LNP with DFHack "Enhanced Gameplay", "Other Automation Plugins", "Performance Tweaks", "Stonesense Isometric view"
-I use no other "Hacks"
-I use a custom Tile-pack but this should not be the problem
-I tried Autosaving (with LNP) with the same result
-I saved with "Compressed Saves" until then just fine and tried also without compressing
-I imported the save to a Vanilla version of DF, without the LNP, with the same result
-I tried an older back-up file of the same fortress without that crash happening on LNP and Vanilla
-I embarked on version 0.44.12
-I assume it is either a RAM or Stackoverflow issue but I can't prove that
-I've got 8 GB RAM and a i7-2670QM CPU
|It happens when I try it as well. I looked for militia equipment corruption and found none, nor did the issue go away when all militia was disbanded, so it's probably not a case of the raiding corruption bug.|
Never Raided only used the military recently to defend against Monsters.
Is there a Cap of active Items on the map? I did not understood the difference between Dump and Refuse piles so i have a lot of waste in this fortress. Are there maybe to many Items on the active map?
|Other crashes during saving have been tracked back to a corrupted unit. (0010939)|
I resolved the issue by expelling every entertaining dwarf (bards,poets,dancer) and by waiting some time until they left the area.
I dont know who of them was the problem but I can save again.
In the next note I try to determine which of them is the problem for you to analyze what happened.
edited on: 2019-04-14 23:04
I have no means to prove my observations, but from my experience there are at least two sources of data corruption: one is the infamous military equipment bug, which might be related to the raiding system flaw, and another is about somehow corrupted units, which seemingly tend to be visitors. As both apparently were introduced in .44 i wonder if there is some shared function in the code that defines situations when a military dwarf returns home, or an outsider pays your fort a visit; something like inventory recalculation.
|2019-04-13 01:15||elfricko||New Issue|
|2019-04-13 22:41||elfricko||Tag Attached: 0.44.12|
|2019-04-14 01:06||PatrikLundell||Note Added: 0039320|
|2019-04-14 10:45||elfricko||Note Added: 0039323|
|2019-04-14 11:09||Loci||Note Added: 0039324|
|2019-04-14 11:09||Loci||Relationship added||related to 0010939|
|2019-04-14 19:30||elfricko||Note Added: 0039328|
|2019-04-14 23:02||risusinf||Note Added: 0039329|
|2019-04-14 23:04||risusinf||Note Edited: 0039329||View Revisions|
|Copyright © 2000 - 2010 MantisBT Group|