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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment