MantisBT - VCMI
View Issue Details
0000266VCMIMechanics - Battlespublic2009-12-01 00:152010-07-13 10:55
Zamolxis 
Tow dragon 
normalcrashrandom
closedfixed 
0.74c 
 
0000266: Crash when trying to move Troll
VCMI crashed whey I tried to move a Troll in battle. It could be though that the crash has nothing to do with the Troll, but perhaps be caused by a combination of two known bugs:
- VCMI already calculating the next AI moves (an losses) before our creature moves
- Crash in killing last enemy creature in retaliation

My Troll was the last creature to move in the turn. After his move, it was the turn of enemy's last remaining stack, which probably would have been killed in retaliation. And as I've noticed VCMI tends to already calculate AI's next move (even for the 2nd round while the last creature of round 1 still has to move - not the case here though), I suspect that may be the cause of the crash.
Unfortunately VCMI didn't create .dmp files for this one. The only think I have is the log report attached. If you want to try to reproduce it, it was with Sir Mullich's army in the map attached to 0000183, while battling the Orange hero below him. But it may not help you much, as I've done almost 10 attempts to recreate the crash and failed every time.
No tags attached.
7z BattleCrashOnTrollTurn.7z (1,610) 2009-12-01 00:15
https://bugs.vcmi.eu/file_download.php?file_id=123&type=bug
jpg 2009-12-25_2ndCrashWhenTrollWasGivenMoveInx.jpg (174,676) 2009-12-25 01:25
https://bugs.vcmi.eu/file_download.php?file_id=189&type=bug
jpg

7z 2009-12-25_2ndCrashWhenTrollWasGivenMoveInx.7z (53,108) 2009-12-25 01:25
https://bugs.vcmi.eu/file_download.php?file_id=190&type=bug
Issue History
2009-12-01 00:15ZamolxisNew Issue
2009-12-01 00:15ZamolxisFile Added: BattleCrashOnTrollTurn.7z
2009-12-01 00:24ZamolxisDescription Updatedbug_revision_view_page.php?rev_id=421#r421
2009-12-25 01:24ZamolxisNote Added: 0000483
2009-12-25 01:24ZamolxisReproducibilityunable to reproduce => random
2009-12-25 01:24ZamolxisSummaryCrash when trying to move Troll (unable to reproduce and probably not related to the Troll) => Crash when trying to move Troll
2009-12-25 01:25ZamolxisFile Added: 2009-12-25_2ndCrashWhenTrollWasGivenMoveInx.jpg
2009-12-25 01:25ZamolxisFile Added: 2009-12-25_2ndCrashWhenTrollWasGivenMoveInx.7z
2009-12-25 01:26ZamolxisNote Edited: 0000483bug_revision_view_page.php?bugnote_id=483#r498
2009-12-25 01:27ZamolxisNote Edited: 0000483bug_revision_view_page.php?bugnote_id=483#r499
2010-07-13 10:03Tow dragonNote Added: 0001069
2010-07-13 10:03Tow dragonStatusassigned => closed
2010-07-13 10:03Tow dragonResolutionopen => suspended
2010-07-13 10:52ZamolxisResolutionsuspended => fixed
2010-07-13 10:52ZamolxisDescription Updatedbug_revision_view_page.php?rev_id=956#r956
2010-07-13 10:55ZamolxisNote Added: 0001075

Notes
(0000483)
Zamolxis   
2009-12-25 01:24   
(edited on: 2009-12-25 01:27)
It happened again. See newly attached screenshot & logs (archive includes saved game as well). Again no .dmp file was created.

To try to reproduce (as it's hardly possible), load the attached game and attack the orange hero with Sir Mullich. In the battle, I simply attacked with all troops in round 1, until Troll's turn came. When I gave the Troll the instruction to move to the shaded hex (see screenshot) the game crashed.

I can't find a pattern though:
- I fought the battle 10 more times, trying to use the same actions, I had the crash only 3 times
- The 3 times it crashed were in battles started with (Mass) Slow. However there was a 4th battle which started with (Mass) Slow, that didn't crash on Troll's move, so casting may be a misleading path.

(0001069)
Tow dragon   
2010-07-13 10:03   
I think it's possible that I've fixed it since 0.74c. Please report if this reoccurs.
(0001075)
Zamolxis   
2010-07-13 10:55   
Actually I'm pretty sure it's fixed. I must have played over 100 battles with Sir Mullich's army on that map the last 6 months, and it never occurred again. So I guess some other fix worked on this as well. I will of course report if it reoccurs, but I'll mark it as fixed for now.