Search Issue Tracker
Fixed
Fixed in 6000.3.0f1
Votes
0
Found in
6000.3.0f1
Issue ID
UUM-129273
Regression
Yes
Crash / freeze on "RaiseException" and "Could not allocate memory" error when importing a specific SVG file
How to reproduce:
1. Create a new project with any pipeline
2. Drag and drop the attached “svg1“ SVG file into the Assets folder
3. Close the “Could not allocate memory" pop up message
4. Observe the crash / freeze
Reproducible with: 6000.3.0a5 (f9a1fab5607a), 6000.3.0f1 (820bc0c5f094)
Fixed in: 6000.3.0f1 (5dac2ad68189)
Not reproducible with: 6000.0.63f1, 6000.2.15f1, 6000.3.0a4, 6000.3.0f1 (d1870ce95baf), 6000.4.0b1, 6000.5.0a3
Reproduced on: Windows 11
Not reproduced on: No other environment tested
First few lines of the stack trace:
0x00007FFAA131804A (KERNELBASE) RaiseException
0x00007FF9C87D0C56 (Unity) LaunchBugReporter
0x00007FF9C893BF4F (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FF9C893CA70 (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FF9C79100AD (Unity) DebugStringToFilePostprocessedStacktrace
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [WebGPU] clearing 2d array texture only clears first slice
- Particle System Renderer icon is missing in Animation window > Add Property context menu
- [Android] Legacy, TMP and UI Toolkit Input Field language toggle to some non-latin alphabet languages does not work with external keyboard
- Crash on keywords::LocalKeywordState::operator when calling ShaderUtil.GetPasskeywords with ShaderType.RayTracing set as the third parameter
- Inconsistent “Remove property” behavior when removing child properties in Animator window
Add comment