MegaGlest Forum

MegaGlest => Bug reports => Topic started by: tomreyn on 19 October 2013, 09:35:20

Title: r4616: Crash after lag on Windows 7-64
Post by: tomreyn on 19 October 2013, 09:35:20
Lyra (Windows 7 SP1 with all Windows updates installed, 64-bit, using the CI snapshot, client) and I (atibox, full build from my svn working copy, hosting) were testing r4616 when she started lagging a lot (this is most likely due to her Internet connection, not a bug). MegaGlest then crashed on her system:

Code: [Select]
megaglest.exe v3.8.0-dev
Compiled using: VC++: 1600 on: Oct 19 2013 10:07:17 platform: Windows endianness: little
SVN: [Rev: 4616] - using STREFLOP [SSE] - [no-denormals]
*Note: Monitoring Network CRC NORMAL synchronization...
[] *ERROR* In [..\..\source\shared_lib\sources\platform\posix\socket.cpp::Shared::Platform::Socket::receive Line: 1442] additionalBytes == -1
[] *ERROR* In [network_interface.cpp::Glest::Game::NetworkInterface::DisplayErrorMessage Line: 171] sErr [Player lyra, disconnected from the game.]
[] *ERROR* In [..\..\source\glest_game\network\client_interface.cpp::Glest::Game::ClientInterfaceThread::execute Line: 152] Error [Error receiving NetworkMessage, dataReceived = 4, dataSize = 39
Stack Trace:
00000000 00000000 00000000 ab8d6041 ZwGetContextThread!ntdll (null)(0) +18
00000000 00000000 00000000 ab8d6041 ZwGetContextThread!ntdll (null)(0) +18
]

======= In MinidumpCallback...

***ERROR details captured:
Crash minidump folder: C:\Users\TheAdmin\AppData\Roaming\megaglest\
file: 0cdb257f-4085-482c-baaf-3c04628fd7ab.dmp
Succeeded: 1

(It would be great if we could get more user friendly output here.)

I looked into her DMP file (http://www.sendspace.com/file/32id90) and got this stack trace:
http://megaglest.nopaste.dk/p63139
Title: Re: r4616: Crash after lag on Windows 7-64
Post by: softcoder on 29 October 2013, 22:36:50
Do we have reproducible steps for this defect?
Title: Re: r4616: Crash after lag on Windows 7-64
Post by: tomreyn on 8 November 2013, 02:16:34
I'm afraid not. I was hoping the stack trace I generated from the DMP file would be useful.