[New Heat System causes memory leak]

I recently flew a plane about 1/4 of the way around Kerbin. I never got very fast, I don't think I ever saw mach 1 in fact. Due to the hardcoding of the temp display to F10 (my "record" key) I had the gauges on for the whole flight.

I had the new non-retractable landing gear on the plane, and some time during the flight the temperature gauge popped up on them. 3 gauges, about halfway up. They also had a very light glow.

After I landed, my Kerbal got out of the plane, took his surface science, and I recovered him. The game crashed. The log showed an OOM error.

So at least in this case, high temperature or "lots of gauges" was not the cause.

Same issue here. However, I never landed as the fixed rear gear seems to have that issue any time that speeds exceed 260m/s for an extended time and didn't seem to disturb the performance and I thought the crashes were just KSP being KSP. However, the issue seems to be replicated pretty easily by building a basic jet with the fixed rear gear and the throttle maxed for an extended flight.

Repeating portion of the log just before the game crashed due to OOM:

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

[Experiments]: FX Modules set: 0

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

[Experiments]: Setting FX Modules to 1...

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

[PlanetariumCamera]: Focus: KSP Surveyor II

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

Maneuver Mode enabled

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

Camera Mode: AUTO

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

Active Vessel is in atmosphere. Cannot save.

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

Active Vessel is in atmosphere. Cannot save.

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

Active Vessel is in atmosphere. Cannot save.

(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

DynamicHeapAllocator out of memory - Could not get memory for large allocationCould not allocate memory: System out of memory!

Trying to allocate: 59004B with 4 alignment. MemoryLabel: Physics

Allocation happend at: Line:97 in

Memory overview

[ ALLOC_DEFAULT ] used: 1240767441B | peak: 0B | reserved: 1414243522B

[ ALLOC_GFX ] used: 480413441B | peak: 0B | reserved: 576143136B

[ ALLOC_CACHEOBJECTS ] used: 68284B | peak: 0B | reserved: 12582912B

[ ALLOC_TYPETREE ] used: 13172B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 833436B | peak: 0B | reserved: 8388608B

Could not allocate memory: System out of memory!

Trying to allocate: 59004B with 4 alignment. MemoryLabel: Physics

Allocation happend at: Line:97 in

Memory overview

[[1.0][Release-5-0][April 28, 2015] Active Texture Management - Save RAM!]

Used the new ATM 24.2 release for x64. Can confirm that it works. Current stable release crashed for me (Basic).