| Anonymous | Login | Signup for a new account | 2024-12-27 04:02 PST |  |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update | |
| 0005948 | Dwarf Fortress | Dwarf Mode -- Jobs, Hauling | public | 2012-05-24 11:30 | 2012-05-27 18:24 | |
| Reporter | ag | |||||
| Assigned To | Toady One | |||||
| Priority | normal | Severity | crash | Reproducibility | always | |
| Status | resolved | Resolution | fixed | |||
| Platform | OS | OS Version | ||||
| Product Version | 0.34.10 | |||||
| Target Version | Fixed in Version | 0.34.11 | ||||
| Summary | 0005948: Detaching container from a Store In Bin/Barrel job causes crash in combining code. | |||||
| Description | When the target container used in a new-style batch Store In Bin/Barrel job is removed, it causes a crash in the code used to detect if an item can be combined into an already existing job. | |||||
| Steps To Reproduce | Ensure there are many pending items to store that suddenly get the opportunity; wait until a suitable combined job is in progress, and forbid the container. As soon as the code tries to stockpile another item, it will crash. | |||||
| Additional Information | When the container is forbidden, it is immediately removed from the job; but the job itself only gets a flag set, and would be cancelled at a later point. Meanwhile, the loop that searches for a suitable job to combine into does not check this flag, and assumes there always is a container item attached. When it fails to find an item reference of type 2, it crashes trying to access a NULL pointer. This explains the crash mentioned in bug 0005937. | |||||
| Tags | No tags attached. | |||||
| Attached Files | ||||||
 Relationships |
 Notes |
|
|
(0022705) Footkerchief (manager) 2012-05-24 12:00 |
Unless I'm misunderstanding something, this is a duplicate of 0005937. If you find information that explains an existing report, it's more helpful to post that information at the existing report than to create a new report. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2012-05-24 11:30 | ag | New Issue | |
| 2012-05-24 12:00 | Footkerchief | Note Added: 0022704 | |
| 2012-05-24 12:00 | Footkerchief | Note Added: 0022705 | |
| 2012-05-24 12:00 | Footkerchief | Relationship added | duplicate of 0005937 |
| 2012-05-24 12:00 | Footkerchief | Status | new => resolved |
| 2012-05-24 12:00 | Footkerchief | Resolution | open => duplicate |
| 2012-05-24 12:00 | Footkerchief | Assigned To | => Footkerchief |
| 2012-05-24 12:00 | Footkerchief | Note Deleted: 0022704 | |
| 2012-05-24 14:47 | Footkerchief | Assigned To | Footkerchief => |
| 2012-05-24 14:47 | Footkerchief | Status | resolved => new |
| 2012-05-24 15:11 | Footkerchief | Relationship replaced | related to 0005937 |
| 2012-05-27 18:19 | Toady One | Status | new => resolved |
| 2012-05-27 18:19 | Toady One | Fixed in Version | => Next Version |
| 2012-05-27 18:19 | Toady One | Assigned To | => Toady One |
| 2012-05-27 18:24 | Toady One | Status | resolved => assigned |
| 2012-05-27 18:24 | Toady One | Status | assigned => resolved |
| 2012-05-27 18:24 | Toady One | Resolution | duplicate => fixed |
|
Issue History |
| Copyright © 2000 - 2010 MantisBT Group |
 |