Search Issue Tracker
Duplicate
Votes
1
Found in
5.0.0f4
Issue ID
680880
Regression
Yes
OnCollisionEnter causes Unity to crash when there's many collisions
Steps to reproduce:
1. Open attached project's scene "Scene1".
2. Enter play mode.
3. Press and hold space key.
4. Unity crashes (on ~half a box filled usually)
Remove "OnCollisionWithObject.cs" script from Cube game object and Unity won't crash.
Comments (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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Laik
Mar 25, 2015 15:41
Where's the original this is a duplicate of? I've come across the same issue, calling any OnCollision function will cause Unity to crash if there are approximately 132 rigidbody objects. Commenting out the OnCollision(Enter/Exit/Stay) function stops the crashes, even when there are 500+ rigidbodies colliding!
I tested this in 4.6.1 and this crash does NOT occur. It's a new bug introduced in the Unity 5 release.