Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a1
2018.3.0b4
2019.1.0a1
Issue ID
1090199
Regression
Yes
Crash on PhysicsScene2D::IgnoreCollision_Binding when passing GetComponent() which returns null to Physics2D.IgnoreCollision()
How to reproduce:
1. Open the "Physics2D Ignore Collision crash.zip" project
2. Open the "SampleScene.unity" scene
3. Press Play
Actual result: Unity crashes.
Reproducible with: 2019.1.0a9, 2019.1.0a1, 2018.3.0b10, 2018.3.0a1.
Regression introduced in: 2018.3.0a1.
Not reproducible with: 2018.2.16f1, 2018.2.0a1, 2018.1.9f2, 2018.1.0a1, 2017.4.15f1.
----------------------------
Fixed in 2018.3.0b12, 2019.1.0a11.
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.1):
This and other cases of crashes when passing the special null values from GetComponent to APIs has been fixed.