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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment