Strange memory allocation crash

[mreadshaw]

I've been having some random crashes that seem to be connected to memory problems but I can't understand why. The last time it happened I had Task Manager open and on top of KSP and it said KSP was using 2.8GB (my system has 8GB so I more available). I have mods installed but I delete most parts, including models and textures, I've even delete basically all Squad parts. I'm almost certain that the problem isn't me hitting the 3.6GB limit, or at least if it is it is some type of memory leak.

This is an exception that I got right before it crashed last time, I saw it in the debug window but the game kept going for a few more seconds but it most be related. The crash log is below that.

When it crashed I was trying to add a fairly small (30ish part) subassembly to my craft (also 30ish parts).

Any Idea what is going on? Is it a FAR problem? Thanks for any help.

EDIT: Well now I'm not sure I can trust task manager, I just reloaded KSP built the exact same craft, in the VAB it claimed KSP was using 3GB, but once I launched it Task Manager only 700-900 MB was being used! Definitely something fishy going on with memory.

OutOfMemoryException: Out of memory

at (wrapper managed-to-native) UnityEngine.Mesh:get_vertices ()

at ferram4.PartExtensions.FARPartExtensions.GetPartMeshBoundsInPartSpace (.Part part) [0x00000] in <filename unknown>:0

at ferram4.FARPartModule.TriggerPartBoundsUpdate () [0x00000] in <filename unknown>:0

at ferram4.FARPartModule.get_PartBounds () [0x00000] in <filename unknown>:0

at ferram4.FARBasicDragModel.AttachNodeCdAdjust () [0x00000] in <filename unknown>:0

at ferram4.FARBasicDragModel.UpdatePropertiesWithShapeChange () [0x00000] in <filename unknown>:0

at ferram4.FARGlobalControlEditorObject.FindPartsWithoutFARModel (System.Collections.Generic.List`1 editorShip) [0x00000] in <filename unknown>:0

at ferram4.FARGlobalControlEditorObject.UpdateEditorShipModules () [0x00000] in <filename unknown>:0

at ferram4.FARGlobalControlEditorObject.UpdateWingInteractionsEvent (ConstructionEventType type, .Part pEvent) [0x00000] in <filename unknown>:0

at EventData`2[ConstructionEventType,Part].Fire (ConstructionEventType data0, .Part data1) [0x00000] in <filename unknown>:0

at EditorLogic.<SetupFSM>m__B4 () [0x00000] in <filename unknown>:0

at KerbalFSM.RunEvent (.KFSMEvent evt) [0x00000] in <filename unknown>:0

at KerbalFSM.updateFSM (KFSMUpdateMode mode) [0x00000] in <filename unknown>:0

at KerbalFSM.UpdateFSM () [0x00000] in <filename unknown>:0

at EditorLogic.Update () [0x00000] in <filename unknown>:0

DynamicHeapAllocator out of memory - Could not get memory for large allocationCould not allocate memory: System out of memory!

Trying to allocate: 4194304B with 4 alignment. MemoryLabel: STL

Allocation happend at: Line:74 in

Memory overview

[ ALLOC_DEFAULT ] used: 574877084B | peak: 0B | reserved: 619794322B

[ ALLOC_GFX ] used: 405680568B | peak: 0B | reserved: 469568148B

[ ALLOC_CACHEOBJECTS ] used: 458340B | peak: 0B | reserved: 12582912B

[ ALLOC_TYPETREE ] used: 20472B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 772632B | peak: 0B | reserved: 8388608B

Could not allocate memory: System out of memory!

Trying to allocate: 4194304B with 4 alignment. MemoryLabel: STL

Allocation happend at: Line:74 in

Memory overview

[ ALLOC_DEFAULT ] used: 574877084B | peak: 0B | reserved: 619794322B

[ ALLOC_GFX ] used: 405680568B | peak: 0B | reserved: 469568148B

[ ALLOC_CACHEOBJECTS ] used: 458340B | peak: 0B | reserved: 12582912B

[ ALLOC_TYPETREE ] used: 20472B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 772632B | peak: 0B | reserved: 8388608B

(Filename: Line: 909)

Crash!!!

ERROR: Error while initializing dbghelp.dll, GetLastError: 'The operation completed successfully.' (Address: 00000000)

Edited March 10, 2015 by mreadshaw

[McPoisoned]

If your not already using it install the active texture management mod, it significantly reduces the memory usage. For me it helps to delete the module manager cache as well. If nothing of that works consider launching the game with OpenGl, it helps a lot but doesn't work in full screen. (Use -force-opengl as launch option)

[stupid_chris]

You are hitting the 3.4Gb memory limit, but through FAR. Plugins also use memory.

[mreadshaw]

Hmm that is a shame. It has happened again and again KSP was otherwise only using 2.8 GB. Does that mean FAR was trying to allocate 600ish MB of RAM? That seems excessive.

[Curiosity7907]

On 3/10/2015 at 9:26 PM, McPoisoned said:

If your not already using it install the active texture management mod, it significantly reduces the memory usage. For me it helps to delete the module manager cache as well. If nothing of that works consider launching the game with OpenGl, it helps a lot but doesn't work in full screen. (Use -force-opengl as launch option)

In OpenGL the problem gets solved [Exception]: OutOfMemoryException: Out of memory but in Real solar system without that exception real solar system planet would not load.