Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.2.4f1
2023.1.0a26
Issue ID
UUM-24823
Regression
No
Crash on Scripting::ScriptingWrapperFor when opening a project
Reproduction steps:
1. Open the attached “repro-project“
Expected result: the project opens successfully
Actual result: The Editor crashes
Reproducible with: 2022.2.4f1, 2023.1.0a26
Could not test with: 2021.3.17f1 - due to errors in the Console when downgrading the project
Reproduced on: Windows 10 Pro
Note: If the project does not crash after opening, enter Play Mode
First few lines of the stack trace:
{{0x00007ff74d3c96b4 (Unity) purecall }}
{{0x00007ff74af145da (Unity) Scripting::ScriptingWrapperFor }}
{{0x00007ff74ae303bb (Unity) SceneBindings::GetRootGameObjectsInternal }}
{{0x00007ff74a041356 (Unity) Scene_CUSTOM_GetRootGameObjectsInternal }}
{{0x0000022be5dfd9d5 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.SceneManagement.Scene:GetRootGameObjectsInternal (int,object) 7}}
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.