Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
3
Found in
2018.3.0f2
Issue ID
1110897
Regression
Yes
Crash on PhysicsContacts2D::RemoveContact when destroying a GameObject in the play mode
To reproduce:
1. Open attached project
2. Open "Puzzle_Beijing01_10" scene and press play
3. Play till editor crashes.
Actual result: Unity editor crashes
Expected result: Unity editor should not crash
Reproduced with: 2018.3.0a1; 2018.3.1f1; 2019.1.0a1; 2019.1.0a13
Can't check the repro on 2018.2 due to errors.
2017.4 crashing while opening the project
Comments (2)
-
dreambuffer
Mar 22, 2020 16:09
The problem persists in unity 2019.3.2f1
-
viruseg
Aug 19, 2019 07:42
The problem persists in unity 2019.2.1
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
Resolution Note (fix version 2019.2):
This was an issue with the new multi-scene physics where contacts were left orphaned due to removal from scene prior to contacts being fully destroyed.