Search Issue Tracker
Fixed
Fixed in 6000.0.30f1, 6000.1.0a6, 7000.0.0a12
Votes
0
Found in
2021.3.45f1
6000.0.24f1
6000.1.0a1
7000.0.0a35
Issue ID
UUM-85044
Regression
No
Memory usage increases significantly when using Global Search
How to reproduce:
1. Open the “IN-85904_repro“ project
2. Open the Task Manager on your device
3. Press Crtl+K to open Global Search
4. Enter “prefab“ in the search
5. In Task Manager observe the Editor’s memory usage
Expected result: Memory usage does not increase significantly
Actual result: Memory usage increases significantly
Reproducible with: 2021.3.45f1, 6000.0.24f1, 6000.1.0a1
Could not test with: 2022.3.51f1 (asset indexer errors)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
Notes:
- If prefabs are selected and edited (after using search), the memory usage increases further
- Memory leak seems to occur during or after the “Building assets search index“ background process
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
- UI Text color is incorrect when text is rendered on SubMeshUI
- "Invalid SortingGroup index set in Renderer" errors when making many modifications in same frame
- Crash on GizmoBufferSizeHistory::GetBuffer() when opening a specific scene
- RenderTexture is not initialized when it is set as Material's Texture
- Branch node outputs a random value instead of a constant on the false conditon
Resolution Note (fix version 7000.0.0a12):
Search: Reduced memory consumption of Search during indexation. Properly dispose of memory after incremental update.
Resolution Note (fix version 6000.1.0a6):
Search: Reduced memory consumption of Search during indexation. Properly dispose of memory after incremental update.
Resolution Note (fix version 6000.0.30f1):
Search: Reduced memory consumption of Search during indexation. Properly dispose of memory after incremental update.