MantisBT - VCMI
View Issue Details
0000503VCMIGUI - PreGamepublic2010-06-10 08:572010-07-14 00:17
Boulie 
Tow 
normalcrashunable to reproduce
closedunable to reproduce 
0.81 
 
0000503: Carsh after entering main menu from the game.
added logs
No tags attached.
related to 0000353closed Tow Main Menu bug is back. 
zip crash after main menu enter.zip (135,376) 2010-06-10 08:57
https://bugs.vcmi.eu/file_download.php?file_id=420&type=bug
Issue History
2010-06-10 08:57BoulieNew Issue
2010-06-10 08:57BoulieStatusnew => assigned
2010-06-10 08:57BoulieAssigned To => Tow
2010-06-10 08:57BoulieFile Added: crash after main menu enter.zip
2010-06-10 15:32ZamolxisRelationship addedrelated to 0000353
2010-06-10 15:32ZamolxisNote Added: 0000951
2010-06-10 16:44BoulieNote Added: 0000952
2010-07-13 10:42TowNote Added: 0001074
2010-07-13 10:42TowStatusassigned => feedback
2010-07-13 12:32BoulieNote Added: 0001086
2010-07-13 12:32BoulieStatusfeedback => assigned
2010-07-14 00:17TowNote Added: 0001104
2010-07-14 00:17TowStatusassigned => closed
2010-07-14 00:17TowResolutionopen => unable to reproduce

Notes
(0000951)
Zamolxis   
2010-06-10 15:32   
Possibly related (if not duplicate) to 0000353.
(0000952)
Boulie   
2010-06-10 16:44   
Probably,but I've created new issue cause it is new release, and I hope it is always better to have more dump and log files to solve the problem.
(0001074)
Tow   
2010-07-13 10:42   
It seems to be an unique, strange issue. As if some object for adventure interface still was trying to capture mouse input.

Do you remember, if crash occured immediately on entering main menu? Was it shown on the screen?
(0001086)
Boulie   
2010-07-13 12:32   
sorry I forgot to make screenshot before I left VCMI. I'm not really sure in this moment exactly when it happened.
It can be temporally closed and if it happens again it can be opened.
I've played many times from that moment and I didn't get this crash again.
(0001104)
Tow   
2010-07-14 00:17   
So I'll close it for now. Huh, it hurts me every time when I'm closing crashbug with "no repro" resolution...

I'll add more checking in the related code, so even if the issue is not fixed, it'll be easier to identify it in the next build (if it reappear).