Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.32f1
2022.3.13f1
2023.1.20f1
2023.2.0b18
2023.3.0a13
Issue ID
UUM-55560
Regression
No
Crash on BV4_ProcessStreamKajiyaOrderedQ when two dense GameObjects collide
Reproduction steps:
1. Open the attached "crash_IN-59285.zip" project
2. Open the "\Assets\Scenes\SampleScene.unity"
3. Enter the Play Mode
4. Observe the crash
Reproduced with: 2021.3.32f1, 2022.3.13f1, 2023.1.20f1, 2023.2.0b18, 2023.3.0a13
Reproduced on: Windows 10 (22H2)
Not reproduced on: No other environments tested
Notes:
- Reproducible in Player
- The crash occurs because the "Plane" GameObject is moving vertically through the "whatEverObject" GameObject
- Horizontal movement does not cause crashes
- When experimenting with the speed parameter in the "Move Upward (Script)" Component under "Plane" GameObject, the results seemed to suggest that the higher the movement speed of the "Plane" GameObject while moving through the "whatEverObject" GameObject, the lower the chance of the crash
First few lines of stack:
0x00007ff7e94bb0e6 (Unity) BV4_ProcessStreamKajiyaOrderedQ<0,`anonymous namespace'::LeafFunction_RaycastClosest,RayParams>
0x00007ff7e94bbc17 (Unity) BV4_RaycastSingle
0x00007ff7e942b7de (Unity) physx::Gu::raycast_triangleMesh_BV4
0x00007ff7e93cd149 (Unity) raycast_triangleMesh
0x00007ff7e92fb103 (Unity) MultiQueryCallbackphysx::PxRaycastHit::invoke
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
After review we have elected not to address this issue at this time.