New Heat System causes memory leak

[teraflops]

So since the patch yesterday I've noticed that the heat system causes a memory leak and crash. It only occurs when multiple parts become partially overheated(the little meter overlay appears). As soon as two parts reach this state, memory use starts increasing by multiple megabytes/second until the game reaches 4GB of allocation and crashes. Also the parts never cool down. I can reproduce this at will, with or without kerbal engineer installed. Screenshot is attached for reference. Running steam version of ksp on windows 8.1.

[Tarheel1999]

I just checked the forums to report the same thing. My game keeps crashing during a reentry from the Mun. I have 6 parts overheating (4 landing legs and 2 floodlights). My memory usage jumps from 2.2Gb to 3.7Gb during reentry. All stock install (No part mods and I removed Kerbal Engineer and AeroGUI to eliminate them as the source). In addition changing scenes does not release the memory from the leak. To confirm I jettisoned the bottom part of the lander (the part with legs and lights) before the heating began only gained about 200mb of memory.

UPDATE - Using F10 to disable the temperature gauges minimizes/eliminates the memory leak.

Here's the quicksave (lander at about 68km): https://www.dropbox.com/s/32dqyxqn0myrq75/Mun%20Reentry.sfs?dl=0

System - intel i7, Nvidia GTX660, Windows 7

Edited May 2, 2015 by Tarheel1999

[J.Random]

Yup. Stock KSP 1.0.2. As soon as heat gauges show up, game starts leaking like a Niagara Falls. More gauges shown = faster increase in RAM usage. My personal best is CTD at 0:05:05 MET.

[Hyomoto]

I was in the middle of a flight around Kerbin to do an aerial survey when the game crashed. This is pretty distressing but honestly I was able to fly for about ten minutes with three parts overheated. I thought it was also because I had popupwindow enabled which, on my system at least, causes a huge memory leak as well. I assumed it was that, and I really hope it was. Are you guys also using popupwindow?

[Tarheel1999]

I was in the middle of a flight around Kerbin to do an aerial survey when the game crashed. This is pretty distressing but honestly I was able to fly for about ten minutes with three parts overheated. I thought it was also because I had popupwindow enabled which, on my system at least, causes a huge memory leak as well. I assumed it was that, and I really hope it was. Are you guys also using popupwindow?

Nope. And it's almost definitely the temperature gauges as the memory leak is not present when you disable the gauges using F10.

[teraflops]

Thank you! This has been driving me nuts for the past day. Going to try disabling the gauges now.

I just checked the forums to report the same thing. My game keeps crashing during a reentry from the Mun. I have 6 parts overheating (4 landing legs and 2 floodlights). My memory usage jumps from 2.2Gb to 3.7Gb during reentry. All stock install (No part mods and I removed Kerbal Engineer and AeroGUI to eliminate them as the source). In addition changing scenes does not release the memory from the leak. To confirm I jettisoned the bottom part of the lander (the part with legs and lights) before the heating began only gained about 200mb of memory.

UPDATE - Using F10 to disable the temperature gauges minimizes/eliminates the memory leak.

Here's the quicksave (lander at about 68km): https://www.dropbox.com/s/32dqyxqn0myrq75/Mun%20Reentry.sfs?dl=0

System - intel i7, Nvidia GTX660, Windows 7

[Hyomoto]

Hmm, good to know there is at least a workaround.

[Jakalth]

Yep, this issue is quite wide spread. My poor little High speed test bed brought this on during high altitude tests. Not sure where the difference is, but I was able to slow it down enough that all the heat bars vanished from it on 3 occasions during testing, each lasting close to a minute, and were during the same flight. Even with this, the fourth test only went for 15 seconds at high altitude before the game froze. Doesn't seem to be completely consistent in when it crashes or how quickly it eats memory.

[sal_vager]

Also confirmed on Linux.

Updating this in case a new reader finds it, the memory leak is being caused by the PPFX edge highlighting plugin from the Unity3D asset store, disabling PPFX prevents the leak.

Edited May 18, 2015 by sal_vager

[Superfluous J]

1.0.3 here we come...

[Endersmens]

hmmm.....

1.0 comes out, everybody hates on it, so Squad pushes out 1.01 to please the masses....Squad realizes a few things got borked, releases 1.02 to please the masses even more...and cause a massive memory leak bug.

This is why you don't push Squad to please the masses.

[Jakalth]

Best you can do is report an issue, hope they see the issue and can fix it when they have time, and use work a rounds until it can get fixed.(F10 to disable temp guadges in this case)

[rawcode]

I am having this issue also, trying to fly to the north pole with a basic jet engine. No mods. Rear sections starts to heat up and then I eventually get a crash.

[sal_vager]

Turning off the heat gauges "solved" it for me, tap F10

Updating this in case a new reader finds it, the memory leak is being caused by the PPFX edge highlighting plugin from the Unity3D asset store, disabling PPFX prevents the leak.

Edited May 28, 2015 by sal_vager

[thisisbleep]

KSP Version: v1.0.2 (00842 2015.05.01), Win 7 64-bit

What happens: Crash to desktop

Mods/Addons: None

Steps to replicate: Fly towards the North pole in a jet, all landing gear showing signs of overheating (even though not going very fast). Nose pointing about 10' up to maintain a steady altitude of approx. 10,000m and running at 3x speed (4x speed messes up with the aerodynamics/physics and the plane loses balance).

Result: Crash

Fixes/Workarounds: None known

Other Notes/Pictures/Log files:

Files = https://www.dropbox.com/sh/uhfbx6v0xd2ns4d/AAAIAmd5flqlOFbB2GJmMPs4a?dl=0

I bought the game after 1.0 was released, so I cannot say if the latest update caused this or if it is an ongoing issue. Twice I got within sight of the North pole and both times I get a crash, there was also a third time where I paused the game and alt-tabbed out, but when I went to play the game again KSP had closed itself (probably crashed).

PC specs:

CPU: Intel i5-4690 @ 3.5GHz | GPU: Nvidia Gigabyte GTX 970 G1, 4GB | MoBo: Gigabyte G1 Sniper H6 | RAM: Corsair Vengeance 16GB DDR3 | PSU: Corsair CS750M | HDD: Plextor 256GB SSD & WD 4TB HDD | OS: Win 7 Professional, 64-bit | Display: LG 42" TV | Audio: Logitech Z906

[Shadowlord]

I ran into this myself today, and having read about this earlier, used F10 to stop it from growing out of control within a few seconds after the gauges appeared. While descending, I toggled F10 back on several times for a fraction of a second, to see if it was still eating more memory when I did so. It did, until:

When my rocket had gotten down to (IIRC) about 13km, when I hit F10 that time, the memory leak didn't resume, the bars appeared to be grey, and the parts weren't flashing red anymore, either. It definitely wouldn't hurt to have more tests, since this particular result hasn't been reported before as far as I've read.

Also of note, when I recovered the rocket after it landed, all the leaked memory appeared to get freed (it dropped back to ~1550 MB from ~1880). I still had the temperature gauges turned on at the time.

For the record, I had 8 gauges on-screen when I turned it off initially, and they were from 6 of the micro-lander legs (the first ones you unlock in the tech tree), and two of the cheap radial battery packs. I only saw 300 MB of increased memory usage but I hit F10 within a few seconds of the gauges appearing. Nothing was destroyed in re-entry, but they all had flashing red outlines.

[i'm on Windows 8.1 pro 64-bit, if it's relevant, but it probably isn't since someone mentioned it happens on linux too.]

[Daveroski]

Glad to read this.

In career mode. My two best guys testing a space plane.

I knew that if they made orbit that they wouldn't have enough fuel to de-orbit but it was their first orbit attempt with a SSTO

A lot of parts glowing. Even a couple of batteries in the cargo bay

I opened the bay and was just looking at the view of their ship.

A few seconds later the game crashed.

I know when I reload, that there is a good chance that my guys may already be in orbit with bits aglow or just before they made their insertion burn with bits aglow.

Either way, it's looking very crashy for my guys.

[Daveroski]

I noticed you had bits warming up.. Might be related.

http://forum.kerbalspaceprogram.com/threads/118658-New-Heat-System-causes-memory-leak

[thisisbleep]

I noticed you had bits warming up.. Might be related.

http://forum.kerbalspaceprogram.com/threads/118658-New-Heat-System-causes-memory-leak

Yes, I saw this thread after posting: http://forum.kerbalspaceprogram.com/threads/118658-New-Heat-System-causes-memory-leak

F10 fixes it, until the next update is released.

[Mruno]

Yeah. I'm having this issue too while performing visual surveys.

EDIT: Thank you, F10 fixed it

Edited May 3, 2015 by Mruno

[Inglonias]

Oddly enough, I couldn't reproduce this bug with the following steps:

1. Load up a craft.

2. HyperEdit it into orbit

3. HyperEdit the large fuel tank to its maximum temperature

4. Watch as everything attached to it starts to overheat (but doesn't explode, because not enough heat)

5. Wait, watching the debug menu's memory allocation stats

It stays stable at around 680 MB allocated. I'm not having this issue. What's going on here?

As for specs, this is my computer. Yeah, it's technically below minimum specs.

[rexxie101]

Wow, I believe i'm experiencing the same issue...I'll give the f10 thing a try!

[Sandworm]

Lol, time for another "hot" fix.

Seriously, I just saw this myself and it is a proper bug. There is no argument about intent or features. This is a legitimate error that needs to be corrected. A released product with such a leak, after two patches, is just unacceptable.

I had thought I was seeing things when those little rectangles appeared. I thought it was a linux graphical error. Then I found f10 and spent HOURS looking through settings files and testing mods expecting that something on my end was forcing the overlay. I concluded that it was an official "feature" for teaching new players ... only to discover the memory leak which initially I did not tie to the heat overlay. That entire endeavor was a waste of my spare time. We need some official documentation about this stuff so that we can tell bug from default setting.

Edited May 3, 2015 by Sandworm

[SydKhaos]

This is not being seen by 100% of players though....it needs to be narrowed down more ya.

[Sandworm]

This is not being seen by 100% of players though....it needs to be narrowed down more ya.

There is a simple test, whether you are 'seeing' it or not. Just push f10. If is says "Temperature Guages: Disabled" then you have the bug, the temp display has defaulted on when it should have started off. Whether or not you notice the memory leak is another issue.