Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.2.0f3
Issue ID
968454
Regression
Yes
Unity crashes at Scripting::ScriptingWrapperFor when Collider is passed as a reference to OnCollisionEnter function
How to reproduce:
1. Download repro.zip
2. Open "sss" scene
3. Enter play mode
4. Unity crashes when two game objects collide
Result: Unity crashes because in newscript.cs (line 18) we are passing Collision reference to OnCollisionEnter function
Regression first introduced in: 5.6.0b3
Reproducible with: 5.6.4p3, 2017.1.2p3, 2017.2.0p2, 2017.3.0b10, 2018.1.0a5
Not reproducible with: 5.5.5p1, 5.6.0b2
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 "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
- Warnings due to obsolete Object.FindObjectsByType<T> usage and [SerializeReference] are logged when opening the Netcode for Entities setup scene
- Non-standard pointers cannot change Inspector values with arrow controls when crossing Inspector area
- No longer able to change the Toggle or Slider GameObjects' Target Graphic value and a NullReferenceException is thrown when the Target Graphic value is set to None at any point
Add comment