Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0008959Dwarf FortressMiscellaneous Crashespublic2015-05-15 18:052015-07-13 17:49
normalminorhave not tried
resolvedno change required 
macmacos x10.10.3
0008959: Designated some walls to be smoothed and it crashed
(see below)
I had used Dwarf Therapist on it once to set EVERYONE to be smoothers.
Crash report: http://hastebin.com/raw/omuzonosey [^]
No tags attached.
Issue History
2015-05-15 18:05schlakeNew Issue
2015-05-15 18:55lethosorNote Added: 0032686
2015-05-15 18:55lethosorAssigned To => lethosor
2015-05-15 18:55lethosorStatusnew => needs feedback
2015-05-15 18:55lethosorAdditional Information Updatedbug_revision_view_page.php?rev_id=13079#r13079
2015-05-15 18:55lethosorDescription Updatedbug_revision_view_page.php?rev_id=13081#r13081
2015-05-15 18:56lethosorDescription Updatedbug_revision_view_page.php?rev_id=13082#r13082
2015-05-15 18:58lethosorNote Edited: 0032686bug_revision_view_page.php?bugnote_id=0032686#r13084
2015-05-16 06:49DetrosNote Added: 0032688
2015-07-11 23:25schlakeNote Added: 0032885
2015-07-11 23:25schlakeStatusneeds feedback => assigned
2015-07-12 10:53DetrosNote Added: 0032893
2015-07-13 13:46lethosorNote Added: 0032901
2015-07-13 14:47DetrosNote Added: 0032903
2015-07-13 17:49lethosorNote Added: 0032904
2015-07-13 17:49lethosorStatusassigned => resolved
2015-07-13 17:49lethosorResolutionopen => no change required

2015-05-15 18:55   
(edited on: 2015-05-15 18:58)
Is this reproducible? Can you upload a save to http://dffd.bay12games.com/? [^]

Also, please avoid posting large crash reports in the bug tracker - they take up a lot of space and can't be collapsed without hiding other important information.
(Edit: Actually, they can't be collapsed at all when posted in the report description.)

2015-05-16 06:49   
Try to check if you are not building any constructions (walls, ramps) in tiles where tree parts are growing. That would be well known issue of 0008719.
2015-07-11 23:25   
I apparently don't get email when people add notes to my ticket!

I think it is reproducible, but it wasn't the smoothing that did it, nor was I building into trees. This is a false alarm, I'll file a new ticket on the real cause.
2015-07-12 10:53   
Schlake filled 0009020 so this issue 0008959 can be closed. As "unable to reproduce", I guess.
2015-07-13 13:46   
What? Was that mentioned on the forums? Just because schlake has opened another report doesn't mean that this one is fixed, and I can't see anything mentioning this in 0009020.
2015-07-13 14:47   
I am just reading that "I think it is reproducible, but it wasn't the smoothing that did it, nor was I building into trees. __This is a false alarm__, I'll file a new ticket on the real cause." in 0008959:0032885 as "I now think something else caused that crash so I will abandon this report and make a new one." And 0009020 was created just 10 mins after xe wrote here so I think it is still the same issue, just with two seaprate reports from one player.
2015-07-13 17:49   
Okay, thanks - I must have scrolled to the bottom of this page and missed that.

In my opinion, it's fine to open a different issue for a different cause of a crash - reporters can't edit issue descriptions, and it's less confusing to have different problems reported in separate reports.