Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.0.X
Votes
0
Found in
2021.3.8f1
6000.0.10f1
Issue ID
UUM-22443
Regression
No
[Linux] QuickSearch runs out of memory and crashes the Editor when indexing thousands of assets
How to reproduce:
1. Open the user-attached project (U.AutoCopyFiles.zip)
2. Enable "Parallel Import" in: Project Settings > Editor > Asset Pipeline
3. Open the system's terminal in "[Project Path]/Assets/AutoCopyFiles"
4. Run: $python3 ./test.py
5. Return to the Editor
6. Press Ctrl+K to open the Quick Search window to start indexing the assets
7. Open the System Monitor and observe Unity's memory usage
Expected result: the Quick Search successfully indexes all the assets and doesn't run out of memory
Actual result: the Editor runs out of memory (the Editor may also crash)
Reproducible with: 2021.3.8f1
Reproducible on: Ubuntu 18.04, Ubuntu 20.04
Note: the issue is not reproducible 100% of the time and not on all Linux setups
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
We are unable to reproduce this issue on the latest builds of Unity 2022.3 and Unity 6. We increased the number of objects by a factor of 10 just to make sure and were not able to observe the spikes in memory usage described on mac, Windows or Linux.
Resolution Note (6000.0.X):
We are unable to reproduce this issue on the latest builds of Unity 2022.3 and Unity 6. We increased the number of objects by a factor of 10 just to make sure and were not able to observe the spikes in memory usage described on mac, Windows or Linux.