View Issue Details

IDProjectCategoryView StatusLast Update
0031071RunnerPhysicsPublic2021-04-23 14:52
ReporterDanAssigned ToFritz 
PriorityMediumSeverityB - MajorReproducibility100%
Status ClosedResolutionFixed 
Platform-OSWindows 10OS VersionPro x64
Product Version2.2.2 
Target Version2.3.0Fixed in Version2.3.0 
Summary0031071: Physics: Apparent memory leak in rapid instance creation and destruction, can see RAM raise and doesn't fall back
DescriptionThe attached sample shows an apparent memory leak in physics instance creation and destruction, as you can see the RAM usage raise in the debugger graph and this doesn't fall back even after several minutes of letting the game idle.

(You will see large fps_real drops at the same time, but on my machine it's still consistently well over 1,200 FPS and as soon as you let go of the buttons the fps_real shoots back up.)
Steps To Reproduce1. Import and run the attached sample for Windows using the debugger.
2. Hold down W, A and D, and Spacebar and the RMB.
3. Observe the RAM graph will steadily rise (with occasional jumps of 500k or more) from an original idle of abut 10.2MB until you let go of the buttons.
4. Allow the game to idle for a while and observe the RAM usage does not drop.
Repro: 100%
Tagsphysics, Runner
1.4 Found In
2.x Runtime Found In2.2.2.326
2.x Runtime Verified In



2019-06-21 09:24


debuggergraph.png (8,623 bytes)
debuggergraph.png (8,623 bytes)
asteroids_stripped_export.yyz (500,282 bytes)


2019-06-21 09:25

Adminstrator   ~0064233

Still repros in IDE v2.2.3.426 Runtime v2.2.3.338


2021-04-23 14:52

Adminstrator   ~0065774

Fixed ages ago. Closing.