Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
2
Found in
2018.2.14f1
Issue ID
1093649
Regression
No
Unity runtime has huge memory leak while rendering in batchmode on desktop platforms
To reproduce:
1) Open attached project and scene
2) Build a standalone player (tested on all three)
3) Run it normally
Expected: No leaking, the memory normalizes after a few seconds of running.
4) Run it with -batchmode argument
Actual: A massive memory leak can be seen (speed depends on the version, with newer versions leaking faster, but the slowest was still roughly a gigabyte every 5 seconds)
Reproduced in 2017.4.0f1, 2018.1.0f1, 2018.2.13f1, 2019.1.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Joint Physics result in unexpected behaviors when used for articulated vehicles like buses or trucks
- Standalone Player crashes with "TDerived GetOrLoad<TDerived>() where TDerived : T" when IL2CPP Code generation is set to "Faster (smaller) Builds"
- IndexOutOfRangeException and InvalidOperationException when logging XML string
- Script missing in "Assets/Settings/Mobile_Renderer/GlobalVolumeFeature" of "com.unity.template.urp-blank" template
- “Font Asset Creator - Error Code [Invalid_File_Structure]…“ error is logged when generating Font Assets from fonts which worked with TMP Font Asset Creator
Add comment