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
- Errors when rendering a camera to render texture with only depth
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
Add comment