Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2019.3.0f1
2020.1
Issue ID
1205356
Regression
No
Exception is thrown when destroying Inspector locked Game object before assembly reload
How to reproduce:
1. Open the attached project ("DestroyOnReloadBug.zip")
2. Open the SampleScene scene
3. Open Inspector window
4. In Hierarchy window select "DestroyOnReload" Game object
5. Click on the padlock icon at top-right of the Inspector window
6. Reimport the "DestroyOnReloadBehavior.cs" script
Expected result: No exceptions are thrown
Actual result: Exceptions are thrown in the console
Reproducible with: 2017.4.35f1, 2018.4.14f1, 2019.2.15f1, 2019.3.0f3, 2020.1.0a17
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2020.1.X):
This bug cannot be fixed as a game object is being destroyed during a domain reload through a script attached to the project and this workflow is not valid. Hence, resolving the case as 'Won't Fix'.