You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Play the game on your Windows 7 64bit
2. Read some help screens multiple times
3. the background becomes white
4. Try to click the back button (bottom-left X)
What is the expected output? What do you see instead?
After I read some of the help screens, the background becomes white, then the
game freezes, and I've got an "Xenowar.exe stopped working" alert
What version of the product are you using? On what operating system?
Release v2.5 719 Windows. Windows 7 64bit. I've didn't experienced this on my
Android only on Windows.
Please provide any additional information below.
"Unhandled exception at 0x0041cb48 in Xenowar.exe: 0xc0000005: Access violation
writing location 0x00000016"
Debugging:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\crt\src\mlock.c: 375 line
(void __cdecl _unlock)
Stack Trace:
Xenowar.exe!0041cb48()
[Frames below may be incorrect and/or missing, no symbols loaded for Xenowar.exe]
Xenowar.exe!0041dc5d()
Xenowar.exe!0044d59e()
> msvcr100.dll!_unlock(int locknum=520) Line 375 C
msvcr100.dll!__matherr_flag() + 0x1dc0 bytes C
msvcr100.dll!_unlock(int locknum=18) Line 375 C
msvcr100.dll!_unlock_file(_iobuf * pf=0x5c763048) Line 313 + 0xe bytes C
msvcr100.dll!setvbuf(_iobuf * str=0x00000000, char * buffer=0x00000008, int type=1638032, unsigned int size=1997249893) Line 151 + 0x8 bytes C
msvcr100.dll!setvbuf(_iobuf * str=0x00000000, char * buffer=0x00000008, int type=1638032, unsigned int size=1997249893) Line 155 + 0x5 bytes C
00000004()
msvcr100.dll!_unlock(int locknum=8) Line 375 C
msvcr100.dll!_unlockexit() Line 785 + 0x7 bytes C
msvcr100.dll!_onexit(int (void)* func=0x0046aca4) Line 90 + 0x5 bytes C
Xenowar.exe!0046ac38()
Original issue reported on code.google.com by [email protected] on 10 Nov 2011 at 9:36
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 10 Nov 2011 at 9:36The text was updated successfully, but these errors were encountered: