Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X
Votes
0
Found in
2022.3.63f1
6000.0.51f1
6000.1.7f1
6000.2.0b5
Issue ID
UUM-109088
Regression
No
Crash on Collider::FindNewAttached when colliding specifc GameObjects
How to reproduce:
1. Open the attached “IN-102662_CrashRepro“ project
2. Open the “Assets/Scenes/MatanNewPlayground.unity“ Scene
3. Enter Play Mode
4. Hold one of the yellow circle GameObjects from the triangle shape and drag it to the middle yellow circle Gameobject
5. Repeat the 4th step with the other two yellow circle GameObjects that formed the triangle
6. If Unity hasn’t crashed yet, hold and drag one of the GameObjects that are stacked on top of each other
Reproducible with: 2022.3.63f1, 6000.0.51f1, 6000.1.7f1, 6000.2.0b5
Reproducible on: macOS 15.5 Sequoia (Intel), Windows 11 (by user)
Not reproducible on: No other environment tested
First few lines of the stack trace:
0x00007FFEB1B17478 (Unity) Collider::FindNewAttached
0x00007FFEB1B1980E (Unity) Collider::ParentingChanged
0x00007FFEB1B48241 (Unity) PhysicsManager::HandleColliderHierarchyChanges
0x00007FFEB1AB834F (Unity) TransformHierarchyChangeDispatch::DispatchSelfAndAllChildren
0x00007FFEB1AAF9B7 (Unity) Transform::SetParent
0x00007FFEB1ABD54E (Unity) SetParent
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Add comment