MantisBT

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000086VCMIOtherpublic2009-10-04 12:112010-05-30 03:11
ReporterTow dragon 
Assigned ToTow 
PrioritynormalSeveritycrashReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version0.73 
Target VersionFixed in Version0.74 
Summary0000086: Crash when hitting F4 in 1600x1200 resolution (0.73#4 - different than the F4 crash in lower resolutions reported before)
DescriptionSee the forum link in the Additional Information box below, for the attachment with the crash logs (including the .dmp files after the crash):



This is different from 0000056 (0.72b#15), where in 1024x768 resolution the game goes in full screen without a crash. It only crashes once we try to perform any action in the game. After the crash, both log files are updated, as well as VCMI_client.exe_crashinfo.dmp. VCMI_server.exe_crashinfo.dmp however remains unchanged (based on the file date/hour).



For this one (0.73#4), in 1600x1200 resolution the game crashes already when we press F4. Only the log files are updated. Both VCMI_client.exe_crashinfo.dmp & VCMI_server.exe_crashinfo.dmp remain unchanged.



If you check the date/time of the files in the 1600x1200 F4 Crash logs archive, we have the following:

> VCMI_Client_log.txt & VCMI_Server_log.txt - updated 02-08-2009 @ 1.42 AM - time of the crash in 1600x1200 mode

> VCMI_client.exe_crashinfo.dmp - updated 02-08-2009 @ 1.26 AM - time of the crash in 1024x768 mode

> VCMI_server.exe_crashinfo.dmp - updated 01-08-2009 @ 23.55 PM - no idea what generated this file, as I don't remember other crashes than the F4 tests (might be interesting for you guys to look into it)
Additional InformationOriginally reported here: http://forum.vcmi.eu/viewtopic.php?p=3158#3158 [^]
TagsNo tags attached.
Attached Files

- Relationships
related to 0000049closedTow F4 causing crashes in 0.72 

-  Notes
(0000124)
Zamolxis (viewer)
2009-10-17 22:34
edited on: 2009-11-07 11:26

I've tried to reproduce it in 0.74 and it has been fixed. As my screen indeed does not support the resolution, the console is now displaying an error message accordingly: "Error: SDL says that 1600x1200 resolution is not available!"

Most probably fixed by the changes made by Tow before 0.73c (he mentioned sth about it back then, so I guess whatever he did, it worked;)

(0000210)
Tow (developer)
2009-11-13 16:30

It's great it's finally fixed.
It was an evil, unreproducible for me bug - the worst possible type. ;)
(0000459)
Zamolxis (viewer)
2009-12-22 16:22

Verified and confirmed as fixed in 0.75

- Issue History
Date Modified Username Field Change
2009-10-04 12:11 Tow dragon New Issue
2009-10-17 22:29 Zamolxis Severity minor => crash
2009-10-17 22:29 Zamolxis Reproducibility have not tried => always
2009-10-17 22:29 Zamolxis Summary # 04 Crash when hitting F4 in 1600x1200 resolution - different than the F4 crash in lower resolutions reported before. => Crash when hitting F4 in 1600x1200 resolution (0.73#4 - different than the F4 crash in lower resolutions reported before)
2009-10-17 22:29 Zamolxis Description Updated View Revisions
2009-10-17 22:34 Zamolxis Note Added: 0000124
2009-10-17 22:34 Zamolxis Status new => resolved
2009-10-17 22:34 Zamolxis Fixed in Version => 0.74
2009-10-17 22:34 Zamolxis Resolution open => fixed
2009-10-17 22:34 Zamolxis Assigned To => Zamolxis
2009-10-17 22:34 Zamolxis Status resolved => closed
2009-11-07 11:25 Zamolxis Note Edited: 0000124 View Revisions
2009-11-07 11:26 Zamolxis Note Edited: 0000124 View Revisions
2009-11-13 16:30 Tow Note Added: 0000210
2009-11-13 16:30 Tow Status closed => resolved
2009-11-14 02:13 Zamolxis Relationship added related to 0000049
2009-12-22 16:22 Zamolxis Note Added: 0000459
2009-12-22 16:22 Zamolxis Status resolved => closed
2010-05-29 19:49 Zamolxis Product Version => 0.73
2010-05-30 03:11 Zamolxis Assigned To Zamolxis => Tow

Site | Forums | Wiki | Slack | GitHub


Copyright © 2000 - 2024 MantisBT Team
Hosting provided by DigitalOcean