Search Issue Tracker
Fixed
Fixed in 6000.0.18f1, 7000.0.0a1
Votes
5
Found in
6000.0.16f1
Issue ID
UUM-78661
Regression
Yes
Crash on PopulateContacts when many collisions are made simultaneously
How to reproduce:
1. Open the “IN-82725_repro“ project
2. Open the “Level“ scene
3. Enter Play mode and wait for around 5 seconds
Expected result: The Editor continues to run
Actual result: The Editor crashes
Reproducible with: 6000.0.14f1, 6000.0.16f1
Not reproducible with: 2021.3.43f1, 2022.3.44f1, 6000.0.13f1
Reproducible on: Windows 10, macOS 14.4.1 M2 (user’s device)
Not reproducible on: No other environment tested
First few lines of the Stack Trace:
0x00007FFC3E4A177A (Unity) PopulateContacts
0x00007FFC3E49EF04 (Unity) PhysicsManager2D::ConvertCollision2DToScripting
0x00007FFC3DC1D681 (Unity) SetupArgumentsForMessageInvocation
0x00007FFC3DC1774A (Unity) MonoBehaviour::HandleNotifications
0x00007FFC3D501320 (Unity) GameObject::SendMessageAny
Notes:
- Not reproducible in Player
- If the issue does not reproduce, exit the Play mode and enter again
Comments (3)
-
argibaltzi
Aug 28, 2024 14:58
this needs to be fixed urgently, we have this crash on a finished game ready for shipping!
-
MyrDovh
Aug 26, 2024 22:13
It is reproducible in the Player (tested on iOS)!
-
Andreas010
Aug 24, 2024 17:45
I experience this issue in Player too
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 JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note (fix version 6000.0.18f1):
Fix for this issue will be available on Unity 6000.0.18f1 and above