Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.5.0b6
Issue ID
837921
Regression
No
Reloading scene after it was merged by UnityYAMLMerge tool causes Editor to crash
Editor crashes only in versions where SceneManager exists.
Repro steps:
1. Add some project to perforce (version control system)
2. Add a scene and submit
3. Add GameObject to the scene on remote machine and submit
4. Add GameObject to the scene on local machine and submit
==>
Conflict appears
5. Right-click on the scene in Version Control window and choose "Resolve Conflicts"
6. Choose "Semantic Merge"
7. After merging the scene will be reloaded automatically (sometimes the confirmation dialog appears , then press "Reload")
==>
Editor crashes
According to the callstack this is the SceneManager problem (maybe this class just doesn't expect scene changing in the backgorund) but I cannot repro this without using perforce
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Only the left screen is rendering when using Render Graph Fullscreen Blit in Meta Quest 2
- Context menu with the "Revert" option doesn't appear when pressing the right mouse button on a "Vector2" or "Vector3" property in the Inspector of a custom shader
- Missing Render Feature "Full Screen Pass Render Feature" in any “Universal Renderer Data” asset when upgrading from 2022.3
- Inconsistent ParticleSystemVertexStream.PercentageAlongTrail data range in Trail Texture Modes except "Stretch"
- The Graph Debug Window can be right clicked through and the Node Workspace is manipulated instead
Add comment