Search Issue Tracker
Duplicate
Votes
0
Found in
5.6.1f1
Issue ID
914092
Regression
No
Unity crashes when calling GameObject.Destroy() on an "empty" GameObject
Description:
This crash happens when calling GameObject.Destroy() on an "empty" GameObject that has a VectorLine from the Vectrosity add-in added to it.
To reproduce:
1. Open project.
2. Open scene "CrashScene".
3. Enter Play Mode.
4. Wait a couple of seconds.
Expected results: Game objects are created continuously.
Actual results: Unity crash after a few Destroy calls.
Reproduces with: 5.4.5p2; 5.5.3p3; 5.6.1f1; 5.6.1p1; 2017.2.0a1;
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
This is a duplicate of issue #863131