Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
5.6.0f3
Issue ID
928294
Regression
No
Crash in RuntimeSceneManager::SetActiveScene when discarding change on a deleted scene that is opened in the Hierarchy
To reproduce:
1. Open the project, attached by the tester (sceneCrash.zip)
2. Make sure that scene1 and scene2 are open at the same time
3. Delete Directional Light game object from scene2
4. Delete the scene2 asset from the Project
5. Right click on scene2 in the Hierarchy and press Discard Changes
6. In the dialog, press OK
Expected: discarding changes for the scene that doesn't exist should not crash the Editor. Alternatively, Editor should know when the scene was removed from the project and should close it and remove from the Hierarchy automatically
Reproduced in 5.5.4f1, 5.5.2f1, 5.6.0f3, 5.6.2p2, 2017.1.0f3, 2017.2.0b2
Fixed in 2017.3.0a5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment