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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #863131