How to tell if a crash happened due to Memory constraints

[Kobymaru]

Hi!

"Recently", I am having frequent crashes on Scene changes from and to the KSC view. I don't have hard numbers, but I would estimate that launching/reverting to editor works about 5 times, then it crashes. For me that is more or less reproducible, and is getting increasingly annoying because it really breaks immersion if you have to start up KSP 2-3 times during one play session.

I have quite a few mods installed, but I assume still less part mods than other people.

Obviously, my first thought was "those #!@& memory leaks! stupid  #!@& unity, stupid  #!@& 32 bit". However, I would like to check if it *indeed* was a memory related crash.

What are the signs of such a crash? Does it say "out of memory" somewhere in the logs or in the crash report? I certainly couldn't find it.
If the crash is a mods fault, is there an easy way to figure out which one it is? Because quite frankly, I'm not about to do a binary disect with a Bug that happens sometimes, sometimes not, but when it happens it takes an undefined amount of actions.

 

My mods:

Spoiler

KSP: 1.0.5 (Win32) - Unity: 4.6.4f1 - OS: Windows 8.1  (6.3.10240) 64bit
USI Tools - 0.5.4
Community Resource Pack - 0.4.8
Firespitter - 7.1.5
Kerbal Attachment System - 0.5.5
Kerbal Engineer Redux - 1.0.18
Kerbal Inventory System - 1.2.3
KSP-AVC Plugin - 1.1.5
Docking Port Alignment Indicator - 6.2
NearFutureElectrical - 0.6.1
PartCommander - 1.0.3
RCS Build Aid - 0.7.6
RemoteTech - 1.6.9
Trajectories - 1.4.5
Kerbal Alarm Clock - 3.5
Alternate Resource Panel - 2.7.4
USI Core - 0.1.2
Freight Transport Tech - 0.4.3
Karibou - 0.1.1
UKS - 0.31.12
USI-LS - 0.2.1
USI Survivability Pack - 0.3.3
Universal Storage - 1.1.0.8
Waypoint Manager - 2.4.4

an example crash: https://dl.dropboxusercontent.com/u/1414175/ksp/2016-01-05_153106.zip

Regards, Kobymaru

[proteasome]

Try installing the Graphic Memory Monitor plugin. When your RAM starts getting high it will change from white, to orange, to eventually red lettering.

[Stone Blue]

Open the error.log file and at the top, it shows the RAM usage when KSP crashed...

[Kobymaru]

3 hours ago, Stone Blue said:

Open the error.log file and at the top, it shows the RAM usage when KSP crashed...

81% memory in use.
0 MB physical memory [1522 MB free].
0 MB paging file [2209 MB free].
0 MB user address space [127 MB free].

Soo... It used absolutely no memory? Or KSP-32bit used 81% of my 8GB system memory? Or KSP used 81% of the allowed maximum memory for a 32-bit process?

I'm confused here.

 

11 hours ago, proteasome said:

Try installing the Graphic Memory Monitor plugin. When your RAM starts getting high it will change from white, to orange, to eventually red lettering.

Thanks, I installed it and I will try to keep an eye on the values.

Edited January 7, 2016 by Kobymaru

[NathanKell]

Better to read the output_log.txt  / player.log from the bottom up, and see what was going on before the crash. If there's an ALLOC failure (Windows, maybe linux) or a malloc failure (OSX, maybe linux), it's a memory issue.