Search Issue Tracker
Fixed
Votes
11
Found in [Package]
0.0.12-preview.31
Issue ID
1151798
Regression
No
ECS RenderMeshSystemV2 has substantial amount of memory leak
How to reproduce:
1. Open the attached project ("Empty06.zip") or (case_1151798-Empty06_2020.zip if you have problem opening with latest trunk)
2. Open the repro scene ("SampleScene")
3. Enter Play Mode
4. Inspect Profiler's "Memory" tab
Expected results: Memory usage stays relatively the same
Actual results: Memory usage gradually increases
Reproducible with: 2019.1.2f1, 2019.2.0b1, 2019.3.0a2
Couldn't test with 2017.4 and 2018.4, as they don't support required ECS version
Reproducible with package versions: 0.12-preview.31
Note:
After exiting the Play Mode, the allocated memory remains in-use
-
richterk
Nov 30, 2019 03:57
I can confirm this is still in the latest package. Is there any idea of when this will be fixed? Is it yet part of the roadmap for a release?
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
- Awake is called in a different order when IProcessSceneWithReport.OnProcessScene() is called in the Editor and the Build
- LightEvent.AfterShadowMap CommandBuffer events are not being called when race condition occurs
- GUI Items are not found and highlighted when using Highligher.Highlight() method
- Opening a nested Prefab consisting of two prefabs results in a corrupted and broken prefab which becomes a Prefab variant.
- Visual C# Compiler fails to locate assembly if response file compiler argument path contains spaces
Resolution Note (fix version ):
Fixed in Unity Versions 2019.3.0f6, 2020.1.0a18 and above