Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.54f1
Issue ID
UUM-91103
Regression
No
[2022.3 only] Crash on AttachAddedComponents when opening a scene or launching Play mode
Reproduction steps:
1. Open the attached project "Repro"
2. Open scene "Scenes/SampleScene"
3. If the Editor doesn't crash after opening the scene, enter Play mode
Expected result: The scene opens up and Play mode is entered
Actual result: The Editor crashes either when opening the scene or when entering Play mode
Reproducible with: 2022.3.54f1, 6000.0.0b15
Not reproducible with: 6000.0.0f1, 6000.0.31f1, 6000.1.0a8
Reproducible on: Windows 11 (User), macOS 15.1.1 (Intel)
Not reproducible on: No other environment tested
Note:
The crash seems to be related to the GameObject "MeetingRoom_001/Text.002" in the scene as removing it stops the Editor from crashing on Play mode, although it might still inconsistently crash on exiting Play mode.
Stacktrace:
0x00007ff7589e4996 (Unity) AttachAddedComponents
0x00007ff7589ee56f (Unity) MergePrefabChanges
0x00007ff7589cf71d (Unity) MergePrefabInternal
0x00007ff7589cbb5d (Unity) MergeAllPrefabInstanceInfosDuringLoad
0x00007ff7589ccd02 (Unity) MergeAllPrefabInstancesDuringLoad
0x00007ff75779191d (Unity) LoadSceneOperation::CompleteAwakeSequence
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
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.