Kerbal Space Program

Eddie, I subscribe to the RSS feed of this bug tracker and you seem to have posted more than your fair share of non-constructive comments lately. It's getting a bit spammy. Please stick to constructive comments such as additional information about work-arounds or how to reproduce the issue.

I've removed non-constructive comments from this issue. Please let me know of any others via ted (at) squad.com.mx.
Additionally, memory leaks stemming from UI will be addressed in the next update which will be using Unity 5, instead of 4.x as previous updates have. Other memory leaks will be solved as we come across them during this upgrade process.

A little information on this issue from my own observations: (This information is based on observations in 1.0.4.861)

The memory leak seems to be tied to any scene change or camera switching event. Using a memory tracker, a consistent amount of ram is eaten and not freed up after any of the following:
- Scene Changes:
-- Spaceport to VAB
-- VAB to Spaceport
-- Spaceport to SPH
-- SPH to Spaceport
-- Spaceport, VAB or SPH to Flight Scene
-- Flight Scene to VAB, SPH, or Spaceport
-- Flight to Inflight-Map
-- Inflight-Map to Flight
-- Tracking Station to Flight
-- Flight to Tracking Station

Additionally, in the VAB or SPH, ram may also be lost either from loading part menus, or creating and removing parts.

Overall, the amount of RAM consumed by any major camera swap or scene change activity seems to depend on the complexity of the scene in terms of graphics and texture. Swapping out between flight and VAB for early rockets, as an example, generally consumes less ram and allows for a great many more swaps than later, larger vessels. Likewise, any mods that increase scene graphics and textures, such as planet and cloud texture mods, cause greater ram consumption between changes of relevant scenes.

Obviously, heavily-modded installs will suffer more if they are part or graphics heavy. Not only because they increase the base amount of ram being used to begin with, but because graphical instances like the parts menus in the VAB/SPH are more densely populated with a wide variety of graphical components. In observation, a higher part count in a modded install leads to a ram creep that renders the game borderline overloaded after about 20 to 40 minutes in construction going through menus. In scene changes, the memory creep seems to cycle to the tune of about 50-100 mb between major scenes like Spaceport to Flight with smaller leaks from flight to inflight-map and back.

Of additional note: The memory leak did NOT occur for any in-flight traversal of terrain no matter how much distance was covered (This includes an overnight real-time flight of a duplicated global hawk on autopilot: Mod heavy). It also did NOT occur for any in-flight progression of time (time warp or real) spent in a static location, and does not occur in any other scenes in which the game is left idle or otherwise player activity is null.