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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.