Dwarf Fortress Bug Tracker - Dwarf Fortress |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0011105 | Dwarf Fortress | Miscellaneous Crashes | public | 2019-06-05 16:53 | 2019-07-11 18:20 |
|
Reporter | tilia-cordata | |
Assigned To | Loci | |
Priority | normal | Severity | crash | Reproducibility | have not tried |
Status | acknowledged | Resolution | open | |
Platform | Desktop computer (Intel i3-7100) | OS | Ubuntu Linux | OS Version | 18.04 |
Product Version | 0.44.12 | |
Target Version | | Fixed in Version | | |
|
Summary | 0011105: Segmentation fault, uncertain cause |
Description | I'm getting a very consistent crash to desktop in a particular save, but am uncertain of the cause. The save was started while running DFHack (version/release: 0.44.12-r2), but the crash occurs whether or not I use it. Occurs 1-2 minutes into the save file linked.
Last line of errorlog.txt is:
path fail: dwarf,Pickup Equipment,167,70,170 -> 70,121,11: Id #32111:Path Goal Grab Uniform:Station Mill Building at 176,64,173
|
Steps To Reproduce | Open linked save game, un-pause, then wait about 90 seconds.
|
Additional Information | Save file: http://dffd.bay12games.com/file.php?id=14404 [^]
Stacktrace: https://pastebin.com/JiaSvPcU [^] |
Tags | No tags attached. |
Relationships | |
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2019-06-05 16:53 | tilia-cordata | New Issue | |
2019-06-05 21:33 | risusinf | Note Added: 0039390 | |
2019-06-07 02:50 | risusinf | Note Edited: 0039390 | bug_revision_view_page.php?bugnote_id=0039390#r16058 |
2019-06-11 17:59 | tilia-cordata | Note Added: 0039392 | |
2019-07-11 18:20 | Loci | Note Added: 0039430 | |
2019-07-11 18:20 | Loci | Assigned To | => Loci |
2019-07-11 18:20 | Loci | Status | new => acknowledged |
Notes |
|
(0039390)
|
risusinf
|
2019-06-05 21:33
(edited on: 2019-06-07 02:50) |
|
No military, no visitors, so no expected explanations. Dies in 80-85sec, managed to resave it few seconds away from crashing. Trying to investigate.
============
It doesn't seem to be related to any creatures or their activities, at least exterminating and borrowing don't fix it. After some poking with debugger i guess there is some kind of a timer that loops perfectly in my test fort, but makes a wrong call in this one. The loop takes slightly longer than in my fort, so it should have something to do with worldgen/embark parameters like its size, probably. I don't see what else could be done here.
|
|
|
|
It must be something with the worldgen - I retired the wonky fort and tried to start a new one, game seg-faulted immediately. |
|
|
(0039430)
|
Loci
|
2019-07-11 18:20
|
|
The provided save crashes for me as well. |
|