Memory Leak question

[pincushionman]

I just read through the changelog on the forum, and I only saw "memory leak" mentioned wrt ground scatter; not with scene change or with tweakables.

I might have read over it, but …any thoughts?

[Brotoro]

Maybe they called it something else.

[Fel]

I just read through the changelog on the forum, and I only saw "memory leak" mentioned wrt ground scatter; not with scene change or with tweakables.

I might have read over it, but …any thoughts?

"Memory Leak" is "human readable", not really a programming term (it's a symptom of a problem, not the problem itself)

For instance, lets say a few resources never unloaded correctly between VAB switching but at the start of the switch you call to load the resources again, while this does create a "memory leak" the leak is a symptom, the problem was that resources were never fully unloaded. Why they weren't unloaded can also turn the not-unloading into a symptom, given the way unity and C# works; if the "problem" lies with how C# handles variables, then making work arounds to that would fix a "memory leak" but now we're barely talking about the initial leak but improvements on garbage collection.

Edited April 27, 2015 by Fel

[crparris]

so... the big question since im at work and cant test it myself:

is it fixed?

[LadyAthena]

so... the big question since im at work and cant test it myself:

is it fixed?

I don't see a memory leak in 1.0 It has consistently stayed under 2 GB useage and has never peaked past that. It also drops when I go into the VAB, etc. after flight.

[crparris]

I don't see a memory leak in 1.0 It has consistently stayed under 2 GB useage and has never peaked past that. It also drops when I go into the VAB, etc. after flight.

that is the best news i have heard all day.

thanks!

[Nobody_1707]

Well, the 'memory leak' is not a leak per se

It's just that in some cases, the game does not free memory it no longer needs. So when these unfreed memory starts to accumulate, while the game keeps requesting new free memory, you soon hit the 32bit memory limits (for the 32 bit client of course) once that happens, the OS will start using the hard drives as a cache, slowing down the game tremendeously (most os's aren't suited to address more memory than that) - or outright crashing the game.

Just so that everyone is on the same page, not freeing memory that you no longer need is the very definition of a memory leak.

[Anister]

KSP 1.0 uses a new texture format, decreasing memory footprint, giving more space for mods...

[Kegereneku]

So far my old XP is bugging like hell, I can't access any building in KSP if I don't -force-opengl and I lag like hell as soon as atmospheric effect kick-in.

Still looking for the right option to play normally.

Edit : My problems was solved doing this.

Open up your Settings.cfg file in Notepad and look for the TEXTURE_QUALITY line. Change this value to 1 (so it reads TEXTURE_QUALITY = 1) and save the file. Then try to run KSP again.

Some of the default settings were overwritten in 0.90, causing the textures to take up more memory than necessary in some cases.

Edited April 28, 2015 by Kegereneku

[Instresu]

I've found an odd memory leak in the VAB. It has nothing to do with KSP itself, though, but Kerbal Engineer Redux. Uninstalling it solved my problems.