Can anyone confirm if my KSP is crashing due to hitting the memory barrier?

[Honeybadga]

I keep getting constant crashes with my modded 32-bit KSP 0.90 installment. The application is hitting the 3.7 - 3.8 GB mark with me trying to get a 30 part rocket into orbit. When I enter my VAB in career mode and load the rocket, KSP is already at around 3.4ish GB. Because I'm $h!t and I need a couple of tries to get that thing into orbit with FAR, everytime I do revert to launch, memory usage keeps increasing until after the 5th or so try, the game crashes at around 3.78ish GB. Could this be a memory leak?

After some months of absence, I finally wanted to play KSP again with all the awesome new features for the career mode and I remember that in the past, the game was running fine for me with a good bunch of mods that added even more parts than the installment I'm currently running. Right now I'm very early into career mode and this is a real bummer. I'm trying to avoid to run Active Texture Management in the aggressive setting since the textures look ....ty then, but perhaps I won't have any other choice.

Apologies advance for the following little rant: I consider KSP to be one of the best if not THE best game ever made, I've sunk hundreds (probably 1000+) hours into it, but these technical issues are really holding the game back. KSP's recommended system requirements of 4 GB have nothing to do with reality. [/rant]

Is there any word if we can expect things to get better with the 1.0 release? I've already read Ted's post about Windows 64-bit builds for KSP so I'm not counting on a stable 64-bit version anytime soon, but still, as I've already mentioned, I remember things have been better before.

Here are some logs from three instances of the application crashing:

https://www.dropbox.com/s/6m8mqu44d6x0jzl/2015-04-05_033706.rar

https://www.dropbox.com/s/pj0m4qntk86r9mz/2015-04-05_035540.rar

https://www.dropbox.com/s/ks4aylmsc8f1utz/2015-04-05_044748.rar

Most of this stuff is hieroglyphs to me.

List of mods:

ActiveTextureManagement 32bit Basic

Alternate_Resource_Panel-2.6.3.0

Atmospheric Trajectories-1.1.3

B9_Aerospace_Pack-R5.2.8

EnhancedNavBall_1_3_5

EnvironmentalVisualEnhancements-7-4

Ferram_Aerospace_Research-v0.14.7

Infernal_Robotics_Model_Rework_-_Core_Pack-v01

Infernal_Robotics_Model_Rework_-_Expansion_Pack-v01

Infernal_Robotics_Model_Rework_-_Utility_Pack-v01

IR.Rework.P2

Karbonite_0.5.5

KAS_0.4.10

Kerbal_Alarm_Clock-3.2.4.0

Kerbal_Joint_Reinforcement-v3.1.2

KIS_v1.0.1

KSPX-v0.2.8.1

KW_Rocketry-2.6d2

Mark_IV_Spaceplane_System-1.1.2

MechJeb2-2.4.2.0

ModuleManager-2.5.13

Navball_Docking_Alignment_Indicator-6

Near_Future_Construction-0.4.0

Near_Future_Electrical-0.3.1

Near_Future_Propulsion-0.4.0

Near_Future_Solar-0.4.0

Near_Future_Spacecraft_Parts-0.3.1

Procedural_Wings-0.9.3

ProcFairings_3.11

RCSBuildAid_v0.6.1

RealChute_Parachute_Systems-1.3.1

RemoteTech-1.6.3

SCANsat-v10.0

ScienceAlert-1.8.4

TacFuelBalancer_2.4.1.1008

Toolbar-1.7.8

TweakScale_-_Rescale_Everything-v1.52.1

Here's a screen grab of my game data folder:

My system specs:

Windows 7 Ultimate 64-bit SP1

Intel Core i7 930 @ 2.8 GHz

6 GB RAM

Zotac GTX470 AMP!

3 Samsung HDDs, no SSDs

Edited April 5, 2015 by Honeybadga

[dewin]

Based your post and my own observed crashes, you're definitely crashing due to memory.

I see you already have AdvancedTextureManagement in your mod list. You might try setting your texture resolution to half and/or using more aggressive settings for ATM to squeeze out a bit more memory.

Alternatively, the -force-d3d11 or -force-opengl launch options may help with memory usage -- but you may notice some pretty significant graphical glitches.

Lastly, you can try removing some texture-heavy mods.

Regardless of all this, there does appear to be a memory leak so this merely buys more time between crashes. Whether the leak is stock or an addon or both is anybody's guess though.

[Windspren]

Do you have the patcher in your ksp file? You should delete it as it made my KSP load in 30 seconds. Also, you can make a folder in your gamedata called Part Packs. Move your part mods inside of there and KSP loads way faster

[Honeybadga]

Based your post and my own observed crashes, you're definitely crashing due to memory.

I see you already have AdvancedTextureManagement in your mod list. You might try setting your texture resolution to half and/or using more aggressive settings for ATM to squeeze out a bit more memory.

Alternatively, the -force-d3d11 or -force-opengl launch options may help with memory usage -- but you may notice some pretty significant graphical glitches.

Lastly, you can try removing some texture-heavy mods.

Regardless of all this, there does appear to be a memory leak so this merely buys more time between crashes. Whether the leak is stock or an addon or both is anybody's guess though.

I did indeed set ActiveTextureManagement to aggressive but as you already said, it only buys more time between crashes. With ATM basic, from startup to going to the VAB in my career save I was already looking at 3.4 GB RAM usage. ATM's aggessive setting bought me around 500MB of RAM. However, KSP's memory usage keeps increasing for me with each change of scenery which includes going from VAB to the starting ramp, doing revert flight back to both start or the VAB, quickloading, finishing a mission etc. This results in me having to restart the game between most successful flights or just waiting for it to crash and then restart.

I have tried starting it with the openGL parameter but it doesn't really help due to my video card having an issue with it. As I've said, I've been running heaviliy modded installs of KSP in the past with a good bunch of more texture heavy mods than I do now but it has never been as bad.

Do you have the patcher in your ksp file? You should delete it as it made my KSP load in 30 seconds. Also, you can make a folder in your gamedata called Part Packs. Move your part mods inside of there and KSP loads way faster

KPS's loading time isn't really that much of an issue for me since once ActiveTextureManagement compresses the textures, it doesn't take that long for the game to load during the consecutive starts. I'm not sure what you mean by the patcher. Also, I'm not sure if I feel comfortable with altering the folder structure of mods like B9.

[dewin]

I did indeed set ActiveTextureManagement to aggressive but as you already said, it only buys more time between crashes. With ATM basic, from startup to going to the VAB in my career save I was already looking at 3.4 GB RAM usage. ATM's aggessive setting bought me around 500MB of RAM. However, KSP's memory usage keeps increasing for me with each change of scenery which includes going from VAB to the starting ramp, doing revert flight back to both start or the VAB, quickloading, finishing a mission etc. This results in me having to restart the game between most successful flights or just waiting for it to crash and then restart.

I've also ran into this problem, FWIW, and I use to be able to run a much heavier install in 0.22/0.23 as well.

My hope is that I can free up some memory so I can at least go longer between crashes/restarts. (Actually, now I'm on a project to see if I can get KSP to play nice in a 64-bit Linux VM so I can play it without dual-booting, but there's already a topic for that.)

[helaeon]

I'm using DDS Loader and the DDS tool found in the forums and no AFT. NearFuture and the MK4 spaceplane can have their textures dropped to 1/2 if DDSed and you won't likely notice but you'll save a TON of memory. You may want to do something similar to B9 and KW.

Also forcing openGL is pretty much mandatory as far as I can tell.

[bernh]

Here's the solution I came up with - http://forum.kerbalspaceprogram.com/threads/115069-0-90-Possible-Windows-Memory-Wall-Crash-Workaround

It is similar to what helaeon is suggesting, but I am adding in an extra step in the form of a RAM optimizer. I still couldn't get past the loading screen until I added the RAM optimizer into the mix.

[ColKlonk]

I see you already have AdvancedTextureManagement in your mod list. You might try setting your texture resolution to half and/or using more aggressive settings for ATM to squeeze out a bit more memory.

I have a good one with regard to ATM... running KSP under OpenGL.

ATM under 2x compression was messing up my instruments so I dumped it... and gained 100MBs of memory.. interesting .

I regularly cleaned ATMs cache as I tried and deleted mods, so there was never any leftover images that loaded unnecessary.

Edited April 9, 2015 by ColKlonk