Skip to content

Potential memory leak detected by KSPCF #139

@rekterakathom

Description

@rekterakathom

The following is being spammed into the logs by KSPCF. In my latest log I counted ~700 instances of the following in 2 hours of gameplay:

[LOG 00:41:21.068] [KSPCF:MemoryLeaks] A destroyed SystemHeat:ReactorToolbar instance is owning a onGUIApplicationLauncherUnreadifying callback. No action has been taken, but unless this mod is relying on this pattern, this is likely a memory leak.
[LOG 00:41:21.069] [KSPCF:MemoryLeaks] A destroyed SystemHeat:ReactorToolbar instance is owning a onGUIApplicationLauncherDestroyed callback. No action has been taken, but unless this mod is relying on this pattern, this is likely a memory leak.
[LOG 00:41:21.069] [KSPCF:MemoryLeaks] A destroyed SystemHeat:SystemHeatOverlay instance is owning a onEditorLoad callback. No action has been taken, but unless this mod is relying on this pattern, this is likely a memory leak.
[LOG 00:41:21.069] [KSPCF:MemoryLeaks] A destroyed SystemHeat:SystemHeatEditor instance is owning a onAboutToSaveShip callback. No action has been taken, but unless this mod is relying on this pattern, this is likely a memory leak.

Eventually my game crashed due to "Unexpected mark stack overflow" from the GC.

Mod version is 0.8.2

Full log:

KSP-memleak-log.zip

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions