Starting a third game in row always results in IE

Bug #1060872 reported by Starkku
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ares
New
Undecided
Unassigned

Bug Description

Basically I play two games with my mod, after which I attempt start a third one. Game will then always give Internal Error, usually before the loading screen appears, altough sometimes it appears for a very short time before screen turns black and error dialog pops up. So far I've only tested this in skirmish, but I wouldn't be surprised if it happened in multiplayer as well.

Probably the most significant thing to note about this, is that it only happens while I play with my mod. Unmodified YR (even when using Ares) seems unaffected.

Debug & stuff: http://phantom.cncguild.net/downloads/debug/threegamesie.7z

Revision history for this message
Starkku (starkku) wrote :

Oh, I'll just add that this also happens if I play my mod without Ares. Same EIP in the except.txt, even.

Revision history for this message
Starkku (starkku) wrote :

I've figured out the cause of this error. The error in the above except/debug files is actually a false positive. Accoding to Graion Dilach, it has something to do with color schemes, and if I altered the colors in my [Colors] list in such fashion that no color scheme had same HSV values as any other, this error would be substituted with another. Turns out it tried to display error message for this second error all along, but unless I click 'No' (so no crash dump is created) on the dialog for that color scheme error, I don't get to see the second one nor any except/debug files are created for it.

So what was causing the second, this time an actual error? Empty (as in, containing only pixels using color index 0) SHP being used for a TerrainType (trees and such). Not having SHP at all does not cause such error, though. Neither does that aforementioned false positive color scheme issue pop up alone, even if you have duplicate HSV values.

Revision history for this message
Graion Dilach (graiondilach) wrote :

That's... completely stupid. But I guess you are right... and it blown up itself in memory management.

Dunno what to do with the report then.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.