View Issue Details

IDProjectCategoryView StatusLast Update
0008693Dwarf FortressDwarf Mode -- Flowspublic2015-01-05 14:13
Reporterpraptak Assigned Tolethosor  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionnot fixable 
PlatformLinuxOSUbuntu 
Product Version0.40.23 
Summary0008693: Crash on unpause
DescriptionFully reproducible crash on unpause. Will not happen if you delete the only burrow before unpausing.
Steps To ReproduceLoad the save, unpause. Save at: http://dffd.wimbli.com/download.php?id=10373&f=region5.zip
TagsNo tags attached.

Relationships

duplicate of 0008647 resolvedToady One Game Crashes at certain point. 

Activities

ptb_ptb

2015-01-03 03:36

reporter   ~0031655

I've had two unexplained crashes in around 20 game years' play (DF 0.40.23). I was never able to get one to be reproducible, though, so may not be related.

praptak

2015-01-04 05:31

reporter   ~0031685

Experimented some more. It's probably not the burrow but something with the dwarf assigned to it - does not show on the unit list (carpenter shows twice instead), doesn't take jobs. Retiring and unretiring the fortress seems to have fixed this.

Rafal99

2015-01-04 07:39

reporter   ~0031687

Seems to be related to 0008647 (see Toady's note there).

lethosor

2015-01-04 08:34

manager   ~0031688

Last edited: 2015-01-05 14:14

0008647 doesn't seem related to burrows, and destroying burrows shouldn't fix corrupted units/jobs. (Edit: Didn't notice Praptak's note above.) Praptak, what version was this world created in? Has it ever been saved from 0.40.20?

praptak

2015-01-05 00:05

reporter   ~0031696

Correct - this has been saved from 0.40.20.

To be precise - destroying burrows does not fix the (supposedly) corrupt unit/job, it merely prevents the immediate crash. Retiring and unretiring the fortress does seem to fix the unit though.

lethosor

2015-01-05 14:13

manager   ~0031712

Ah, this probably is caused by 0008647 in that case. Thanks! Feel free to reopen this report or PM me on the forums to reopen it if you can determine that this crash is caused by something else.

Issue History

Date Modified Username Field Change
2015-01-03 01:22 praptak New Issue
2015-01-03 03:36 ptb_ptb Note Added: 0031655
2015-01-04 05:31 praptak Note Added: 0031685
2015-01-04 07:39 Rafal99 Note Added: 0031687
2015-01-04 08:34 lethosor Note Added: 0031688
2015-01-04 08:34 lethosor Assigned To => lethosor
2015-01-04 08:34 lethosor Status new => feedback
2015-01-05 00:05 praptak Note Added: 0031696
2015-01-05 00:05 praptak Status feedback => assigned
2015-01-05 14:13 lethosor Note Added: 0031712
2015-01-05 14:13 lethosor Status assigned => resolved
2015-01-05 14:13 lethosor Resolution open => not fixable
2015-01-05 14:13 lethosor Relationship added duplicate of 0008647
2015-01-05 14:14 lethosor Note Edited: 0031688