Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b1
Issue ID
900850
Regression
No
Crash on UnityScene::UnloadSceneObjects when closing scene which was closed on SceneClosingCallback
To reproduce:
1. Download and open attached project.
2. Execute menu item: "BUG/Delete scene"
Crash!
...
EditorSceneManager.sceneClosing += SceneClosingCallback;
// Close any scene here
...
static void SceneClosingCallback(Scene scene, bool remove)
{
EditorSceneManager.sceneClosing -= SceneClosingCallback; // Workaround not to make an infinite loop
EditorSceneManager.CloseScene(scene, true);
EditorSceneManager.sceneClosing += SceneClosingCallback;
}
Closing the same scene on EditorSceneManager.sceneClosing callback will result in closing the same scene twice, will try to free memory which is already freed.
Reproduced on: 2017.1.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Add comment