Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0008959Dwarf FortressMiscellaneous Crashespublic2015-05-15 18:052015-07-13 17:49
Assigned Tolethosor 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusresolvedResolutionno change required 
PlatformmacOSmacos xOS Version10.10.3
Product Version0.40.24 
Target VersionFixed in Version 
Summary0008959: Designated some walls to be smoothed and it crashed
Description(see below)
Additional InformationI had used Dwarf Therapist on it once to set EVERYONE to be smoothers.
Crash report: [^]
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
lethosor (manager)
2015-05-15 18:55
edited on: 2015-05-15 18:58

Is this reproducible? Can you upload a save to [^]

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.)

Detros (manager)
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.
schlake (reporter)
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.
Detros (manager)
2015-07-12 10:53

Schlake filled 0009020 so this issue 0008959 can be closed. As "unable to reproduce", I guess.
lethosor (manager)
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.
Detros (manager)
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.
lethosor (manager)
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.

- Issue History
Date Modified Username Field Change
2015-05-15 18:05 schlake New Issue
2015-05-15 18:55 lethosor Note Added: 0032686
2015-05-15 18:55 lethosor Assigned To => lethosor
2015-05-15 18:55 lethosor Status new => needs feedback
2015-05-15 18:55 lethosor Additional Information Updated View Revisions
2015-05-15 18:55 lethosor Description Updated View Revisions
2015-05-15 18:56 lethosor Description Updated View Revisions
2015-05-15 18:58 lethosor Note Edited: 0032686 View Revisions
2015-05-16 06:49 Detros Note Added: 0032688
2015-07-11 23:25 schlake Note Added: 0032885
2015-07-11 23:25 schlake Status needs feedback => assigned
2015-07-12 10:53 Detros Note Added: 0032893
2015-07-13 13:46 lethosor Note Added: 0032901
2015-07-13 14:47 Detros Note Added: 0032903
2015-07-13 17:49 lethosor Note Added: 0032904
2015-07-13 17:49 lethosor Status assigned => resolved
2015-07-13 17:49 lethosor Resolution open => no change required

Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker