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
- 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
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment