Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2017.2.0b1
Issue ID
923322
Regression
No
Move Game Object To Unloaded scene on scene unloaded callback is possible, and leaves the object without valid scene
To reproduce:
1. Open attached project.
2. Run tests.
Result:
Moving game object to scene (which was unloaded), on sceneUnloaded callback is possible. It succedes, then scene is destroyed but object is not unloaded, it stays without valid scene, floating in space. So if user looses reference to that game object, it won't be possible to destroy it.
Although, if unloaded scene does not have path (it means it come from SceneManager.CreateScene in runtime), then game object is stored in DontDestroyOnLoad scene
Expected result: I think gameObject.scene should always be valid. This operation should not be possible at all, or object should be stored in DontDestroyOnLoad.
Reproduced: 2017.2.0b3 (4c2ac554540c)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment