View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008959 | Dwarf Fortress | Miscellaneous Crashes | public | 2015-05-15 18:05 | 2015-07-13 17:49 |
| Reporter | schlake | Assigned To | lethosor | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | no change required | ||
| Platform | mac | OS | macos x | OS Version | 10.10.3 |
| Product Version | 0.40.24 | ||||
| Summary | 0008959: Designated some walls to be smoothed and it crashed | ||||
| Description | (see below) | ||||
| Additional Information | I had used Dwarf Therapist on it once to set EVERYONE to be smoothers. Crash report: http://hastebin.com/raw/omuzonosey | ||||
| Tags | No tags attached. | ||||
|
|
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.) |
|
|
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. |
|
|
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. |
|
|
Schlake filled 0009020 so this issue 0008959 can be closed. As "unable to reproduce", I guess. |
|
|
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. |
|
|
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. |
|
|
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. |
| 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 => feedback |
| 2015-05-15 18:55 | lethosor | Additional Information Updated | |
| 2015-05-15 18:55 | lethosor | Description Updated | |
| 2015-05-15 18:56 | lethosor | Description Updated | |
| 2015-05-15 18:58 | lethosor | Note Edited: 0032686 | |
| 2015-05-16 06:49 |
|
Note Added: 0032688 | |
| 2015-07-11 23:25 | schlake | Note Added: 0032885 | |
| 2015-07-11 23:25 | schlake | Status | feedback => assigned |
| 2015-07-12 10:53 |
|
Note Added: 0032893 | |
| 2015-07-13 13:46 | lethosor | Note Added: 0032901 | |
| 2015-07-13 14:47 |
|
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 |
