Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2021.1.X
Votes
0
Found in
2019.4.12f1
Issue ID
1327333
Regression
No
Crash when calling "Rigidbody2D.ClosestPoint" on an inactive Rigidbody2D.
Reproduction steps:
1. Open attached project "Physics2D_Closest_Crash_Project.zip" and scene "SampleScene"
2. Enter Play Mode
3. Crash!
Expected result: Should not crash.
Actual result: Crashes.
The physics system is simply not checking if the underlying Box2D body is available or not i.e. checking if it's NULL. This issue has probably been around for many, many years.
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 2021.2):
Rigidbody2D.ClosestPoint now correctly checks for the underlying Box2D body before calculating the closest point.