View Issue Details

IDProjectCategoryView StatusLast Update
0010343Dwarf FortressTechnical -- Saving/Loadingpublic2017-12-18 15:53
ReporterArmokGoB Assigned ToToady One  
PrioritynormalSeveritycrashReproducibilityalways
Status resolvedResolutionfixed 
PlatformWindowsOSWindows 10 HomeOS Version10.0.14393
Product Version0.44.01 
Fixed in Version0.44.03 
Summary0010343: Crash while "rebuilding temporary information"
DescriptionThe game crashes when I try to load this game. It is a fortress mode game. I believe there are less than 50 dwarves and it's a 3x3 embark in a taiga. An artifact was created. Standard changes to init and d_init were made and a graphics pack was installed. No mods
Steps To ReproduceTry to load this save and watch as the game crashes
Additional InformationSave: http://dffd.bay12games.com/file.php?id=13209
TagsNo tags attached.

Activities

Loci

2017-11-24 07:03

viewer   ~0036961

Linked save still crashes in v0.44.02 (though a save generated in v0.44.02 would be helpful to confirm this is unrelated to 0010330).

ArmokGoB

2017-11-25 23:00

reporter   ~0037015

Last edited: 2017-11-25 23:02

With all the crashes involved with art objects, I'm curious to know if all of this is related to looking at art. 0010344 and 0010355 seem awfully suspicious when paired with this. I had a ton of engravings in my meeting area and looked at a few.

FantasticDorf

2017-11-26 03:48

reporter   ~0037019

Yes, it would not be uncommon for the artifact to have a image actively engraved upon it of a dwarf or another being currently affected by the no ID bug 0010344 maybe even the creator itself or a historical figure.

ArmokGoB

2017-11-26 18:00

reporter   ~0037042

Should we mark these as related?

FantasticDorf

2017-11-27 02:54

reporter   ~0037045

Not without further evidence it would actually be the cause, at the given time they are distinct cases.

Toady One

2017-12-18 15:53

administrator   ~0037351

There was a mistake with the error-logging for artifacts that had been offloaded but somehow also were in play. The underlying cause isn't fixed, but it should log properly now without crashing.

Issue History

Date Modified Username Field Change
2017-11-24 00:19 ArmokGoB New Issue
2017-11-24 07:03 Loci Note Added: 0036961
2017-11-24 07:04 Loci Assigned To => Loci
2017-11-24 07:04 Loci Status new => confirmed
2017-11-25 23:00 ArmokGoB Note Added: 0037015
2017-11-25 23:01 ArmokGoB Note Edited: 0037015
2017-11-25 23:02 ArmokGoB Note Edited: 0037015
2017-11-26 03:48 FantasticDorf Note Added: 0037019
2017-11-26 18:00 ArmokGoB Note Added: 0037042
2017-11-27 02:54 FantasticDorf Note Added: 0037045
2017-12-18 15:53 Toady One Note Added: 0037351
2017-12-18 15:53 Toady One Status confirmed => resolved
2017-12-18 15:53 Toady One Fixed in Version => Next Version
2017-12-18 15:53 Toady One Resolution open => fixed
2017-12-18 15:53 Toady One Assigned To Loci => Toady One