0000550: Game freezes if sieged hero casts haste.

Issue History
Date Modified	Username	Field	Change
2010-07-27 08:14	Boulie	New Issue
2010-07-27 08:14	Boulie	Status	new => assigned
2010-07-27 08:14	Boulie	Assigned To	=> Tow dragon
2010-07-27 08:14	Boulie	File Added: siege_01 cast haste.jpg
2010-07-27 18:42	Zamolxis	Severity	minor => major
2010-07-27 22:01	Zamolxis	Note Added: 0001201
2010-07-27 22:01	Zamolxis	Status	assigned => feedback
2010-07-27 22:02	Zamolxis	Note Edited: 0001201	View Revisions
2010-07-28 06:58	Boulie	Note Added: 0001207
2010-07-28 06:58	Boulie	Status	feedback => assigned
2010-07-28 06:58	Boulie	File Added: forced crash after game freezes with haste.zip
2010-07-28 06:58	Boulie	File Added: _test_SoD_map_by Boulie.h3m
2010-07-28 09:47	Boulie	Note Edited: 0001207	View Revisions
2010-07-28 09:47	Boulie	Note Edited: 0001207	View Revisions
2010-07-28 10:14	Tow dragon	Note Added: 0001208
2010-07-28 10:14	Tow dragon	Status	assigned => resolved
2010-07-28 10:14	Tow dragon	Fixed in Version	=> 0.89
2010-07-28 10:14	Tow dragon	Resolution	open => fixed
2014-05-30 17:39	beegee	Status	resolved => closed

Notes
(0001201) Zamolxis (viewer) 2010-07-27 22:01 edited on: 2010-07-27 22:02	I changed the severity because any freeze caused by a normal action in the game qualifies at least as "major" (if not crash, or even block, depending how early in the game we may be forced to run into that). However I tried to reproduce it, but I am able to cast Haste with sieged hero without a problem. So there's more to this bug that what's in the report. Can you try again and see what else may cause it? Maybe type CRASH in the Console when it happens to create a dump or give us a saved game to reproduce.

(0001207) Boulie (reporter) 2010-07-28 06:58 edited on: 2010-07-28 09:47	Added forced crash dump files and test map. Run it in MP, end red turn and attack Castle/Edric (red) with Valeska(blue). During red move cast haste. You can cast it when towers are active.

(0001208) Tow dragon (viewer) 2010-07-28 10:14	fixed in rev 1696. marked as fixed in 0.next because I belive this bug was present in earlier versions.

Relationships