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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment