Search Issue Tracker
Fixed in 2017.2.0f3
Duplicate in 5.6.X, 2017.1.X
Fixed in 5.6.X, 2017.1.X
Votes
0
Found in
5.6.1f1
Issue ID
941997
Regression
No
Memory leak when Development Build is focused after using the Profiler
To reproduce:
1. Create a new project
2. Go to "Build Settings"
3. Enable "Development Build"
4. Press "Build & Run"
5. Go to Editor and enable Profiler, connect it to the build (Connected Player>WindowsPlayer(*))
6. Connect Profiler to Editor and close the Profiler window
7. Open the Task Manager
8. Focus the Build window and observe Memory usage in the Task Manager
Desired outcome: Memory allocation is stable and is not growing.
Actual result: Memory growth for the build keeps increasing continuously when the build is focused.
Reproduced with 5.5.1f1, 5.5.4p3, 5.6.1f1, 5.6.3f1, 2017.1.0p4, 2017.2.0b8
Not reproduced with 2017.3.0a4
Fixed in: 5.6.3p4, 2017.1.1p2, 2017.2.0b10
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- WebGL sends wrong value with large numbers when SendMessage function is used
- Add Behaviour dropdown has a part in which the dropdown outline is cut out when the Add Behaviour dropdown is opened
OmarVectorX
Dec 06, 2017 08:17
The bug still exist in 2017.2.0f3
however, you dont need to do any build, just run inside the editor and the observe the memory usage in task manager when using profile :D