Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b9
Issue ID
922929
Regression
Yes
Editor leaks memory when using the Hierarchy search
To reproduce:
1. Open the project, attached by tester (hierarchyMemoryLeak.zip)
2. Open the "scene" scene
3. In Hierarchy, write "G" in the search bar
4. Observe the memory usage in the Task Manager
5. Remove the "G" letter from the search bar
6. Repeat 3 - 5
Expected: searching in the Hierarchy does not increase the memory usage to abnormal amounts
Actual: with each new search in the Hierarchy, memory usage of the Editor increases
Reproduced in 5.6.1p1, 2017.1.0b9, 2017.1.0b10, 2017.2.0a4
Did not reproduce in 5.6.2f1, 2017.1.0b9
Fixed in 2017.1.0f2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “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
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment