Search Issue Tracker
Fixed
Fixed in 6000.3.0a5
Votes
0
Found in
2022.3.63f1
6000.0.50f1
6000.1.8f1
6000.2.0b6
6000.3.0a1
Issue ID
UUM-109729
Regression
No
Crash on RaiseException when entering Play Mode in a specific project
How to reproduce:
1. Open the attached “IN-102142_CrashRepro“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Enter Play Mode
Reproducible with: 2022.3.63f1, 6000.0.50f1, 6000.1.8f1, 6000.2.0b6
Reproducible on: macOS 15.5 Sequoia (Intel), Windows 10 (by user)
Not reproducible on: No other environment tested
Note: Often crashes when opening the project, and can also crash when opening and then closing the project
First few lines of the stack trace:
0x00007FF8FD89AF29 (KERNELBASE) RaiseException
0x00007FF8844C4593 (Unity) CxxThrowException
0x00007FF8816C6B0E (Unity) std::_Throw_bad_optional_access
0x00007FF8830609AA (Unity) ReloadNativeAssetsNotUpToDate
0x00007FF882F8C8ED (Unity) ImportOutOfDateAssets
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 Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Resolution Note (fix version 6000.3.0a5):
This fix does not make it possible to open the project without deleting the Library folder. Instead, it improves the Unity Editor's ability to detect and handle corruption in certain cases and will better guide you on what your possible steps are.