View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009257 | Dwarf Fortress | Miscellaneous Crashes | public | 2015-12-06 16:08 | 2016-05-16 16:02 |
Reporter | the_immortal_gila_monster | Assigned To | |||
Priority | normal | Severity | crash | Reproducibility | always |
Status | resolved | Resolution | no change required | ||
OS | Linux | OS Version | 4.2.5 | ||
Product Version | 0.42.02 | ||||
Summary | 0009257: All forts crash around Limestone 13. | ||||
Description | I have generated and embarked in multiple worlds in 0.42.01 and 0.42.02. They reliably segfault between 12 and 14 Limestone. The date varies slightly between embarks, but is constant within an embark. If I abandon the fort right before the crash would occur, I can reembark and continue that world for another year, but it crashes again on the next Limestone 13. | ||||
Steps To Reproduce | -generate world -embark -play until 14 limestone. | ||||
Additional Information | Saves (all from 42.02): http://dffd.bay12games.com/file.php?id=11398 (a simple fort) http://dffd.bay12games.com/file.php?id=11399 (a complicated fort) http://dffd.bay12games.com/file.php?id=11402 (a crash in 2nd embark / 2nd year) | ||||
Tags | No tags attached. | ||||
|
Ubuntu 14.04, DF 0.42.02 here, have a fort that's been running for a few years old and never crashed. |
|
Reminder sent to: the_immortal_gila_monster Are you using any 3rd party utilities or mods or is this vanilla DF? |
|
No mods or raw changes, only things like d_init.txt changed. Also the crash still occurs if I move the save to a freshly generated, default config directory. Edit: Just ran one with default config from the start; crashed Limestone 9 |
|
Limestone is the 1st month of autumn so it probably crashes on dwarf trading party coming to your fort. Merchants can be slowed on their way to fort which may cause that variance in date of crash. Is that "a crash in 2nd embark / 2nd year" save showing that "abandoning just before autumn and then reclaiming again" case? |
|
To create the last save I ran a fort until it crashed, continued from a save made immediately before the crash, abandoned the fort to ruin, embarked on a new one in the same world, and played until it crashed again, a year later. |
|
Further research: When embarking with a "dead or dying civilization", a local a dwarf will claim kingship before the first autumn. In these games a caravan does indeed arrive at the time when a crash is expected. No crash occurs. The caravans all arrive with "no outpost laison? how strange!" messages. Subsequent embarks with that civilization still generally crash (note that you don't get a king because the civilization already has one). However I have one save where a dwarf claimed kingship in a second embark, mere days before the caravan arrives (I assume the first king perished in the wilderness). No crash! Furthermore, when rerunning from old saves, he doesn't always claim kingship -- and when he doesn't, the game crashes at caravan time. I conclude: Caravans arrival causes a crash UNLESS you have the king on-site. |
|
This appears fixed in 42.03. Old saves still crash, but worlds generated in 42.03 don't. |
|
Thanks for the follow-up. |
Date Modified | Username | Field | Change |
---|---|---|---|
2015-12-06 16:08 | the_immortal_gila_monster | New Issue | |
2015-12-06 16:58 | Aescula | Note Added: 0033532 | |
2015-12-06 17:15 |
|
Note Added: 0033536 | |
2015-12-06 17:15 |
|
Assigned To | => user11 |
2015-12-06 17:15 |
|
Status | new => feedback |
2015-12-06 17:52 | the_immortal_gila_monster | Note Added: 0033542 | |
2015-12-06 17:52 | the_immortal_gila_monster | Status | feedback => assigned |
2015-12-06 19:10 | the_immortal_gila_monster | Note Edited: 0033542 | |
2015-12-09 03:57 |
|
Note Added: 0033664 | |
2015-12-09 10:23 | the_immortal_gila_monster | Note Added: 0033678 | |
2015-12-12 12:41 | the_immortal_gila_monster | Note Added: 0033813 | |
2015-12-12 14:43 | the_immortal_gila_monster | Note Added: 0033814 | |
2015-12-12 14:43 | the_immortal_gila_monster | Note Edited: 0033814 | |
2016-05-16 16:02 |
|
Note Added: 0035195 | |
2016-05-16 16:02 |
|
Status | assigned => resolved |
2016-05-16 16:02 |
|
Resolution | open => no change required |