Melee Posted January 29, 2023 Share Posted January 29, 2023 (edited) Description: Crash to desktop after 'Mission Completed'. What Happened: Stunned last alien Mentarch in Observer and got 'Mission Completed' and then desktop. Further information: Crash didn't repeat loading last save several times and replaying moves. Windows reported fault module of 'mono.dll'. Faulting application name: Xenonauts2.exe, version: 5.5.6.45850, time stamp: 0x5a4f6fa4 Faulting module name: mono.dll, version: 1.0.0.1, time stamp: 0x59ddee7f Exception code: 0xc000041d Fault offset: 0x00000000001584d0 Faulting process id: 0x63c Faulting application start time: 0x01d9339b6bd5ec5b Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Xenonauts2Playtest\Xenonauts2.exe Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Xenonauts2Playtest\Xenonauts2_Data\Mono\mono.dll Faulting application name: Xenonauts2.exe, version: 5.5.6.45850, time stamp: 0x5a4f6fa4 Faulting module name: mono.dll, version: 1.0.0.1, time stamp: 0x59ddee7f Exception code: 0xc0000005 Fault offset: 0x00000000001584d0 Faulting process id: 0x63c Faulting application start time: 0x01d9339b6bd5ec5b Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Xenonauts2Playtest\Xenonauts2.exe Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Xenonauts2Playtest\Xenonauts2_Data\Mono\mono.dll _output.log quick-118.json Edited January 29, 2023 by Melee Quote Link to comment Share on other sites More sharing options...
Chris Posted January 31, 2023 Share Posted January 31, 2023 On 1/29/2023 at 5:47 AM, Melee said: Description: Crash to desktop after 'Mission Completed'. What Happened: Stunned last alien Mentarch in Observer and got 'Mission Completed' and then desktop. Further information: Crash didn't repeat loading last save several times and replaying moves. Windows reported fault module of 'mono.dll'. Faulting application name: Xenonauts2.exe, version: 5.5.6.45850, time stamp: 0x5a4f6fa4 Faulting module name: mono.dll, version: 1.0.0.1, time stamp: 0x59ddee7f Exception code: 0xc000041d Fault offset: 0x00000000001584d0 Faulting process id: 0x63c Faulting application start time: 0x01d9339b6bd5ec5b Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Xenonauts2Playtest\Xenonauts2.exe Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Xenonauts2Playtest\Xenonauts2_Data\Mono\mono.dll Faulting application name: Xenonauts2.exe, version: 5.5.6.45850, time stamp: 0x5a4f6fa4 Faulting module name: mono.dll, version: 1.0.0.1, time stamp: 0x59ddee7f Exception code: 0xc0000005 Fault offset: 0x00000000001584d0 Faulting process id: 0x63c Faulting application start time: 0x01d9339b6bd5ec5b Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Xenonauts2Playtest\Xenonauts2.exe Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Xenonauts2Playtest\Xenonauts2_Data\Mono\mono.dll _output.log 5.67 MB · 0 downloads quick-118.json 2.02 MB · 0 downloads Had you been playing the game for a while? The memory leak still isn't fixed so if you play for long enough, the game will eventually crash in a non-reproducible way and need to be restarted. How long it takes depends on the specs of your system. I can't see obvious crash in the log so that might be what happened? Quote Link to comment Share on other sites More sharing options...
Melee Posted January 31, 2023 Author Share Posted January 31, 2023 (edited) I'm still running 8GB total RAM (board limit). Usually by the time commit size gets to 12+GB pauses for paging become noticeable and I restart game. I've run to 19+GB before to see if it ever stopped climbing. I don't remember where that mission was in that session. Usually ground missions at start take ~7 GB. Edited January 31, 2023 by Melee Quote Link to comment Share on other sites More sharing options...
Melee Posted February 1, 2023 Author Share Posted February 1, 2023 I just noticed there was a crash dump which didn't generate the notification window when it happened. Attached. crash.dmp error.log output_log.txt Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.