Search Issue Tracker
Fixed in 2020.2
Fixed in 2019.3, 2020.1
Votes
0
Found in
2018.3.0a1
2018.4
2018.4.21f1
2019.3
2020.1
2020.2
Issue ID
1239208
Regression
Yes
Crash on Physics2D_CUSTOM_GetIgnoreCollision when checking Physics2D.GetIgnoreCollision against a null Collider
Reproduction steps:
1. Open the attached project ("1239208.zip")
2. Open "SampleScene"
3. Enter Play mode
Reproducible with: 2018.3.0a1, 2018.4.22f1, 2019.3.12f1, 2020.1.0b8, 2020.2.0a9
Not reproducible with: 2017.4.40f1, 2018.2.0a9
First lines of the stacktrace:
0x00007ff75827c9fd (Unity) Physics2D_CUSTOM_GetIgnoreCollision
0x0000029420f731dd (Mono JIT Code) (wrapper managed-to-native) UnityEngine.Physics2D:GetIgnoreCollision (UnityEngine.Collider2D,UnityEngine.Collider2D)
0x0000029420f730fb (Mono JIT Code) [NewBehaviourScript.cs:10] NewBehaviourScript:Start ()
0x000002944ef76d00 (Mono JIT Code) (wrapper runtime-invoke) object:runtime_invoke_void__this__ (object,intptr,intptr,intptr)
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
- [Windows] The Unity import progress is not shown in the Windows taskbar
- Custom shader creation APIs are missing the AssetImportContext and thus can't handle includes correctly
- 2019.4: PackedMemorySnapshot: nativeObjects.gcHandleIndex contains -1 always
- [Hub] Project "Remove from list" option is behind notifications when selecting the most bottom project in the list
- [Android][Vulkan] Black Screen renders on devices with Adreno 640 and Mali GPU's
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a11
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b9
Resolution Note (fix version 2019.3):
Fixed in 2019.3.14f1