Search Issue Tracker
By Design
Votes
2
Found in
2017.3.1p4
Issue ID
1061345
Regression
No
[Il2CPP][Mono] Garbage Collection causes memory leak
Steps to reproduce:
1. Open user attached project
2. Open and play the scene
3. Click "Create" in "Strong Test" row a few times to raise Mono memory
4. Select "set null" and GC in the first row
5. Observe that Mono memory is not fully cleaned
6. Replay the scene
7. Notice that Mono memory is not released
Reproduced in: 2018.3.0a5, 2018.2.0f2, 2018.1.9f1, 2017.4.7f1, 2017.3.2f1, 2017.2.3f1, 2017.1.3p2
Reproduced on:
Android
Windows standalone
Tested devices:
Sony Xperia Z2 (D6503), 6.0.1, CPU: Snapdragon 801 MSM8974PRO-AB, GPU: Adreno (TM) 330
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
The application memory raises, then goes down after some GC.Collect calls, and returns to a steady state of around 150MB.