Search Issue Tracker
Active
Won't Fix in 2023.2.X
Votes
0
Found in
2023.2.17f1
2023.3.0b10
6000.0.0b13
Issue ID
UUM-68119
Regression
Yes
[TypeCache] Crash on RaiseException when selecting "Quit" in a "Fatal Error!" pop-up
Reproduction steps:
1. Open the attached “repro-project“
2. In the “Fatal Error!“ pop-up select “Quit“
3. Observe the crash
Reproducible with: 2023.2.0a16, 2023.2.17f1, 6000.0.0b13
Not reproducible with: 2021.3.36f1, 2022.3.22f1, 2023.2.0a15
Reproduced on: Windows 10, Windows 11 (by reporter)
Not reproducible on: No other environment tested
Notes:
1. The crash is accompanied by a "Fatal Error!" pop-up indicating a severe memory allocation issue: “Could not allocate memory: System out of memory! Trying to allocate: 274877906944B with 16 alignment“
2. The issue appears to be related to the inclusion of System.Deployment.dll and System.Windows.Forms.dll in the project
First few lines of the stacktrace:
0x00007FFB58455B0C (KERNELBASE) RaiseException
0x00007FFAA0487A92 (Unity) LaunchBugReporter
0x00007FFA9FE96ED7 (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFA9FE97A3F (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFAA0B92E1A (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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2023.2.X):
Closing as Won't fix due to 2023.2 reaching it's EOL.