Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.27f1
2022.3.3f1
2023.1.1f1
Issue ID
UUM-40824
Regression
No
Crash on CollectRecurseObjectDataArrayFromPrefabRoot when loading a scene
Reproduction steps:
1. Open the attached project “CrashRepro“
2. Enter the Play Mode
3. Left-click in the Game view
4. Press the “X“ button
5. Press the “Campaign mode“ button
6. Press the “Ready to fight“ button (bottom right corner)
7. Press the “Start fighting” button (bottom right corner)
Expected result: Different scene is loaded
Actual result: Editor crashes
Reproducible with: 2021.3.27f1, 2022.3.3f1, 2023.1.1f1, 2023.2.0a18
Fixed in: 2023.2.0a19
Reproducible on: Windows 10
First few lines of the Stack Trace:
{noformat}0x00007ff7cf0ea0cc (Unity) CollectRecurseObjectDataArrayFromPrefabRoot
0x00007ff7cf0ea0cc (Unity) CollectRecurseObjectDataArrayFromPrefabRoot
0x00007ff7cf0f0bab (Unity) GetObjectDataArrayFromPrefabRoot
0x00007ff7cf111acc (Unity) UnpackPrefabInstance
0x00007ff7cf111852 (Unity) UnpackAllPrefabInstances
0x00007ff7ce1dbd45 (Unity) LoadSceneOperation::CompleteAwakeSequence{noformat}
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
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
- Unity Hub opens instead of the Unity Editor when launching a project from a Windows command line if a backslash is added to the end of the project path
- "ParseErrorException" is thrown when parsing a float with a very small value from JSON
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.