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
- Editor crashes and a window with "GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)" error is shown when launching a freshly created project
- Editor Windows dragging behavior is erratic/glitchy when a specific multi-display setup is used and the Editor window is not on the main display
- Meta Quest missing an icon in Build Profiles window in U6.0
- Foldout arrow indent is misaligned in the Inspector when used for Arrays or Lists
- Material import pipeline strips properties when it is added with a script
This is a duplicate of issue #863131