Method to find offending memory leak?

[rottielover]

I have quite a few mods, but by use of -force-opengl , DDS converter, and ATM when the game is done loading my RAM usage is about 2.6 gb. However, playing the game, launching one or two small ships (career, so we're talking 30 part count type ships here, nothing major), the ram usage creeps up. My last test I've timed it for 12 min to go from 2.6gb to 3.1 gb used. At this time I just keep Task Manager open on my 2nd screen and wait till I get to about 3.2 then I save and exit and restart, and I'm back to 2.6 ish

Normally I'd go through the process of removing all mods, and installing one at a time until the offender is found, but given that we're now in the post 1.0 days, i thought maybe there is a method out there that would allow me to track down the offending mod.

(Doesn't happen on stock install, and I have my own "mod pak" / list that I'm working from).

Thanks in advance!

EDIT: Changing to "workaround" reasons outlined in below post

Edited July 17, 2015 by rottielover

[Padishar]

There is no direct way of finding out how much memory each mod is using however, it is probably not caused by a mod directly, the stock game has a number of memory "leaks" where the memory usage increases every time you change scene (among others) and the more mods you have installed the more significant the leaks become (and the quicker you get close to the memory limit and start having problems).

Without a list of your mods and/or an output_log.txt, it will be difficult to make any helpful suggestions...

[rottielover]

Thank you for the quickly reply Padishar. I was afraid that the answer was going to be something along those lines.

When you said scene changes I tried flipping between ships by use of the map and switching from vessel to vessel rather than going back to the space center, then to tracking, then to the ship. That seems to have helped somewhat since I'm not changing the scene quite so frequently.

So because of that I'm going to call this as a workaround. If you want to swap between ships, try and use the map view to do so as much as possible. I would also say that you should try to find a way to monitor your memory usage, and save and restart the game once you get close to the limit.

[SAI Peregrinus]

Graphic Memory Monitor + SAVE is my preferred solution. (Actually I also use Jebretary for actual backups, and just use SAVE to autosave every 5 minutes. That saves storage space and also backs up .craft files.)

[rottielover]

Great tip! Thanks

[Gampersnaz]

Is this scene change memory leak being worked on? I'm just thinking of the PS4 port, and how it will affect console users as well. I'd like to think that in a stock game, a person should be able to switch scenes as much as they want with worrying if the game will crash.