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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
The application memory raises, then goes down after some GC.Collect calls, and returns to a steady state of around 150MB.