Search Issue Tracker
Fixed in 2018.3.X
Votes
1
Found in
2017.3.1f1
Issue ID
1017186
Regression
No
Crash on 'DisconnectPrefabInstanceRecursive' when playing the scene
Steps to reproduce:
1. Open user attached project
2. Play the scene
- Editor crashes at this point
0x0000000140713201 (Unity) DisconnectPrefabInstanceRecursive
0x00000001407132C1 (Unity) DisconnectPrefabInstanceRecursive
0x00000001407132C1 (Unity) DisconnectPrefabInstanceRecursive
0x000000014071C572 (Unity) DestroyObjectHighLevel
0x00000001407ACB71 (Unity) DestroyWorldObjects
0x0000000140C8C831 (Unity) EditorSceneManager::RestoreSceneBackups
...
Expected result: editor should not crash when the scene is played
Reproduced in: 2018.2.0a6, 2018.1.0b12, 2017.4.0f1, 2017.3.2f1, 2017.2.2p1, 2017.1.3p2
Fixed in: 2018.3.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
Add comment