View Issue Details

IDProjectCategoryView StatusLast Update
0010253Dwarf FortressMiscellaneous Crashespublic2019-02-16 09:10
Reporterctgarlington Assigned ToLoci  
PrioritynormalSeveritycrashReproducibilityalways
Status resolvedResolutionduplicate 
PlatformWindows 10 x64 
Product Version0.43.05 
Summary0010253: Reproducible crash; zero-size flesh ball
DescriptionIssue in current save, infinitely reproducible, can't find a work around. x64 version, using LNP-ish (current version of DFHack). I've tried disabling both DFHack and setting GRAPHICS:NO, to no effect.

Relatively complex fortress (though not as large as many I've seen), 298 total citizens, >100 animals, broken into first two cave layers (though walled off second. Fair number of outstanding jobs, but nothing absurd going on (dwarfy calculators, waterfalls, etc).
Steps To ReproduceCrash happens upon unpausing, after approximately a minute depending on your FPS, almost immediately after hitting date 260-12-19. Only thing that happens leading up to it are a handful of job completions. Seems to crash at the same time, no matter what jobs complete/things happen prior (had different objects created by jobs, random noble requests, etc).
Additional InformationHow do I upload a save?
Tags0.43.05, 64-bit, crash

Relationships

duplicate of 0008410 resolvedlethosor Crash due to zero-size weasel 

Activities

ctgarlington

2017-06-16 21:37

reporter   ~0036615

Bugged save ---> http://dffd.bay12games.com/file.php?id=12970

lethosor

2017-06-16 21:38

manager   ~0036616

Do you have any traps, particularly weapon traps?

ctgarlington

2017-06-16 21:47

reporter   ~0036617

Additional troubleshooting: Assigned all dwarves to a burrow, stuffed in a store room with barrels. Crash repeated at expected time, as such I suspect it's not job-related (as no jobs were available to be performed in that room).

ctgarlington

2017-06-16 21:49

reporter   ~0036618

Last edited: 2017-06-16 21:49

@lethosor Negative, no weapon traps. I do have a couple cage traps floating around my castle entrances, but I've had close to zero hidden invaders for this fort, and no issues with cage trap functionality thus far.

ctgarlington

2017-06-17 06:50

reporter   ~0036619

Last edited: 2017-06-17 06:50

Additional info:
RAM usage at crash time: 1.82XGB

Ran a clean-all command in case it's in some way caused by contaminants, no effect.

Disabled refuse areas in case it had something to do with an object rotting, no effect.

Triple checked creatures visible on map, nothing strange, nothing near any dwarves which might cause an AI or combat related crash as far as I can tell. Aforementioned burrowing of all dwarves already kind of confirmed this though.

Loci

2017-06-25 19:39

viewer   ~0036633

Crash confirmed reproducible in v0.43.05x32. Removing all hauling routes did not prevent the crash (0009624).

risusinf

2019-02-10 21:36

reporter   ~0039204

44.12@lin64/win64: This resave -- http://dffd.bay12games.com/file.php?id=14244 -- goes for FPE crash in seconds. One of the flesh balls underground (first one in the units list) seems to be bugged. Also see 0010061

lethosor

2019-02-12 12:43

manager   ~0039209

By "bugged" do you mean it's the same issue as 0008410/0010061 (i.e. zero body size)?

risusinf

2019-02-12 18:18

reporter   ~0039210

Last edited: 2019-02-12 21:13

I didn't know how to check body size, but crashing stopped when i exterminated specific flesh ball (it's hidden, so i had to "reveal" the map). There is a pack of them, you need the first one from their unit list section. I linked those issues because they are the only SIGFPE crashes i could find on the tracker.

============

Ok, i put your spells in the magic box, here's what i get

[DFHack]# lua ~unit.body.size_info
<body_size_info: 0x7fffb4b795e4>
size_cur = 0
size_base = 7000
area_cur = 0
area_base = 363
length_cur = 0
length_base = 410

[DFHack]# lua ~unit.id
18579

[DFHack]# lua "for _,u in ipairs(world.units.all) do if u.body.size_info.size_cur == 0 then print(u.id) end end"
18579

Loci

2019-02-16 09:08

viewer   ~0039220

Thank you for investigating!

Issue History

Date Modified Username Field Change
2017-06-16 21:24 ctgarlington New Issue
2017-06-16 21:27 ctgarlington Tag Attached: 0.43.05
2017-06-16 21:27 ctgarlington Tag Attached: 64-bit
2017-06-16 21:27 ctgarlington Tag Attached: crash
2017-06-16 21:37 ctgarlington Note Added: 0036615
2017-06-16 21:38 lethosor Note Added: 0036616
2017-06-16 21:47 ctgarlington Note Added: 0036617
2017-06-16 21:49 ctgarlington Note Added: 0036618
2017-06-16 21:49 ctgarlington Note Edited: 0036618
2017-06-17 06:50 ctgarlington Note Added: 0036619
2017-06-17 06:50 ctgarlington Note Edited: 0036619
2017-06-25 19:39 Loci Note Added: 0036633
2017-06-25 19:39 Loci Assigned To => Loci
2017-06-25 19:39 Loci Status new => confirmed
2019-02-10 21:36 risusinf Note Added: 0039204
2019-02-12 12:43 lethosor Note Added: 0039209
2019-02-12 18:18 risusinf Note Added: 0039210
2019-02-12 18:30 risusinf Note Edited: 0039210
2019-02-12 21:13 risusinf Note Edited: 0039210
2019-02-16 09:08 Loci Note Added: 0039220
2019-02-16 09:08 Loci Relationship added duplicate of 0008410
2019-02-16 09:08 Loci Status confirmed => resolved
2019-02-16 09:08 Loci Resolution open => duplicate
2019-02-16 09:10 Loci Summary Reproducible crash; unknown cause => Reproducible crash; zero-size flesh ball