Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.59f1
6000.2.7f1
6000.3.0b4
6000.4.0a1
6000.5.0a1
Issue ID
UUM-120889
Regression
No
Out of memory crash when selecting more than 80000 Assets simultaneously
Steps to reproduce:
1. Create a new Unity project
2. Download the attached “images.zip” file and extract it (see pinned comment)
3. Upload the “images” folder to Assets and open it
4. Select one of the images and press “command + a” (MacOS) or “Ctrl + a” (Windows)
5. Observe Unity not responding and eventually crashing
Reproducible with versions: 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Reproducible on: macOS 15.6.1 (M1 Max), Windows 11 (user’s)
Not reproducible on: no other environment tested
First few lines of StackTrace:
0x00007FFB40A385EA (KERNELBASE) RaiseException
0x00007FFA94193D56 (Unity) LaunchBugReporter
0x00007FFA93A8437F (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFA93A84EA0 (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFA9470201D (Unity) DebugStringToFilePostprocessedStacktrace
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
Selecting that many objects will load a lot of data which might crash unity depending on memory available.
This is a pretty niche workflow. No time to properly fix.