MegaGlest / megaglest-source

MegaGlest real-time strategy game engine (cross-platform, 3-d)
http://megaglest.org/
349 stars 89 forks source link

Memory related error while playing using Windows 64-bit build #106

Closed tomreyn closed 8 years ago

tomreyn commented 8 years ago

On January 07 I used the Windows 64-bit snapshot build of 35f3b2f (rev 5373, build 144) on Windows 10 running on atibox to take part in a larger multi-player game. Somewhere around the middle of the game, I suddenly got disconnected.

Unfortunately, no useful information to further analyse this issue is available at this time. For completeness, the console output is provided below.

Softcoder suggested that "it is possible (likely) that the [..] assembly stuff for Streflop makes it not stable for x64 Windows".

This bug report is not meant to analyse this incident further, but just to serve as a reminder that more testing needs to go into Windows 64-bit builds before we release.

C:\Users\user1\mg-windows-3.12-dev-develop>megaglestx64.exe
megaglestx64.exe v3.12-dev
Compiled using: VC++: 1900 [64bit] platform: Windows-X64 endianness: little
GIT: [Rev: 5373.35f3b2f] - using STREFLOP [SSE] - [no-denormals]
Auto Change resolution to (1680 x 1050) from (1024 x 768)
curl FAILED with: 78 [Remote file not found] attempting to remove folder contents [C:\Users\user1\AppData\Roaming\megaglest\tilesets/] szBuf [ftp://tilesets_custom:mg_ftp_server@94.23.148.250:63002/.7z] ftpfile.isValidXfer = 0, pathCreated = 0
curl FAILED with: 78 [Remote file not found] attempting to remove folder contents [C:\Users\user1\AppData\Roaming\megaglest\tilesets/] szBuf [ftp://tilesets_custom:mg_ftp_server@94.23.148.250:63002/.7z] ftpfile.isValidXfer = 0, pathCreated = 0
curl FAILED with: 78 [Remote file not found] attempting to remove folder contents [C:\Users\user1\AppData\Roaming\megaglest\tilesets/] szBuf [ftp://tilesets:mg_ftp_server@94.23.148.250:63002/.7z] ftpfile.isValidXfer = 0, pathCreated = 0
Game unique identifier is: 4e876bb6-b575-11e5-9749-21bd62fe72c9
*ERROR* [2016-01-07 20:46:04] In [window.cpp::Shared::Platform::Window::handleEvent Line: 513] (c) Couldn't process event: [UNKNOWN ERROR] codeLocation = h
Error saved to logfile [C:\Users\user1\AppData\Roaming\megaglest\error.log]
*ERROR* [2016-01-07 20:46:05] In [..\..\..\source\glest_game\main\main.cpp::Glest::Game::ExceptionHandler::handleRuntimeError Line: 642] [Unknown error [main]!] gameInitialized = 1, program = 0000000000264590
*ERROR* [2016-01-07 20:46:05] In [..\..\..\source\glest_game\main\main.cpp::Glest::Game::ExceptionHandler::handleRuntimeError Line: 661] [Unknown error [main]!
Stack Trace:
ffffffff 00000000 00130508 4669acf0 NtGetContextThread!ntdll (null)(0) +10
00000000 00130508 4669acf0 0012d880 NtGetContextThread!ntdll (null)(0) +0
00000000 00130508 4669acf0 0012d880 NtGetContextThread!ntdll (null)(0) +0
]
*ERROR* [2016-01-07 20:46:05] In [window.cpp::Shared::Platform::Window::handleEvent Line: 513] (c) Couldn't process event: [UNKNOWN ERROR] codeLocation = g
*ERROR* [2016-01-07 20:46:05] In [window.cpp::Shared::Platform::Window::handleEvent Line: 513] (c) Couldn't process event: [UNKNOWN ERROR] codeLocation = h
*ERROR* [2016-01-07 20:46:05] Access violation. Illegal read by 1078820863 at 165373788159|Unknown module|Unknown function
1190512|Unknown module|Unknown function
1190265|Unknown module|Unknown function
1112|Unknown module|Unknown function
215|Unknown module|Unknown function
4|Unknown mod []
** #2 Socket peek error for sock = 1348 err = 0 lastSocketError = 0 mustGetData = 0
IsConnected socket has disconnected sock = -1 err = 0 lastSocketError = 0

[..\..\..\source\shared_lib\sources\graphics\gl\font_textFTGL.cpp::Shared::Graphics::Gl::TextFTGL::Render] Line 246 Error = 1282 [invalid operation] for text [Deleting]
titiger commented 8 years ago

This turned out not to be reproducable by anyone and the stack does not give too much information. I close this now.

tomreyn commented 8 years ago

I agree - I have not been able to reproduce this since, and the output is very generic (memory corruption) so it's not too useful to retain this report.