0002867: Crash inside squad scheduals during siege

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0002867

Dwarf Fortress

Dwarf Mode -- Interface, Squad Schedule

public

2010-07-27 14:45

2010-07-28 15:21

Reporter

eerr

Assigned To

Footkerchief

Priority

high

Severity

crash

Reproducibility

have not tried

Status

resolved

Resolution

duplicate

Platform

OS Version

Product Version

0.31.08

Target Version

Fixed in Version

Summary

0002867: Crash inside squad scheduals during siege

Description

When rapidly looking at and attempting to modify squad scheduel, my game crashed.

my dwarves were last set to defend the innersanctum, and I was trying to order them to move to a certain spot inside
(an order for every person in the military!)
I accidently left in another order as a higher priority, and wanted to change that.

I pressed a whole bunch of buttons trying to fix the squad menu, and crashed the game right after the order menu lost focus.

order menu-(the one with 'ten dwarves guard burrows')

Steps To Reproduce

? raise siege, scroll through and rapidly change menus very very quickly?

It seemed to happen when I was pressing keys faster than could be resolved in the squad menu.

Or maybe it just hanged for a minute while I stared on in horror.

Additional Information

Goblins ride all sorts of crazy shit.
trolls pop up slowly as the third division.
goblins are either very patient or very close by, because they arrived with the current siege within a month or two after the first maceman+cave swallow commando siege.

Tags

No tags attached.

Attached Files

Relationships

duplicate of

0000706

resolved

Toady One

Trying to access the squad screen mid-combat caused a complete game hang

Notes
(0011170) Rafal99 (reporter) 2010-07-27 15:48	Update your DF to the latest version, there were lots of crash bugs fixed since 0.31.08.

(0011205) Footkerchief (manager) 2010-07-28 15:21	Reminder sent to: eerr This is almost certainly 0000706, which was fixed recently. Reopen this issue if upgrading to 31.12 doesn't fix your problem.

Issue History
Date Modified	Username	Field	Change
2010-07-27 14:45	eerr	New Issue
2010-07-27 15:48	Rafal99	Note Added: 0011170
2010-07-28 15:20	Footkerchief	Tag Attached: AWAITING UPDATE
2010-07-28 15:21	Footkerchief	Note Added: 0011205
2010-07-28 15:21	Footkerchief	Relationship added	duplicate of 0000706
2010-07-28 15:21	Footkerchief	Status	new => resolved
2010-07-28 15:21	Footkerchief	Resolution	open => duplicate
2010-07-28 15:21	Footkerchief	Assigned To	=> Footkerchief
2010-07-28 15:21	Footkerchief	Tag Detached: AWAITING UPDATE