Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0b13
Issue ID
1032594
Regression
Yes
Memory leak when remotely profiling
To reproduce:
1) Create a new project on Windows
2) Build it for a Standalone platform as a development build
3) Launch it on a different machine on the same network
4) Connect to the player from the editor in Windows
5) Check the Unity process's memory usage in task manager or similar app
Expected: No change in memory over time
Actual: Memory rises from 800MB to X GB rapidly (for a new project, 1.3GB, but on a bigger project over 3GB cap was seen, at a rate of roughly 50MB/s), then it drops back to 800MB and rises again, repeating the same behavior endlessly.
Reproduced in 2018.1.0b13, 2018.1.0f2, 2018.2.0b3
Not reproduced in 2018.1.0b7, 2017.4.3f1, 2017.3.0f3
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 JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment