Search Issue Tracker

Fixed

Fixed in 6000.0.42f1, 6000.1.0b9, 6000.2.0a6

Votes

7

Found in

6000.0.34f1

6000.1.0b1

6000.2.0a1

Issue ID

UUM-96080

Regression

Yes

Freeze when calling Rigidbody.SweepTestAll in a specific project

-

How to reproduce:
1. Open the “CrashRepro“ project
2. Open the “Assets/SampleScene.unity“ Scene
3. Enter Play Mode

Reproducible with: 2023.3.0b1, 6000.0.34f1, 6000.1.0b1, 6000.2.0a1
Not reproducible with: 2022.3.56f1, 2023.3.0a19

Reproducible on: macOS 15.2 Sequoai (Intel), Windows 10 (reported by user)
Not reproducible on: No other environment tested

Note: Issue reproducible in Player

  1. Resolution Note (fix version 6000.2.0a6):

    Fixes a stack corruption on SweepTestAll when doing a sweep test on a higher number than 32 colliders in a scene. Also replaced any allocators which use alloca to avoid any potential null expection crashes on IOS. We now allocate the returned hit results in one instance, instead of in a block based manner, which caused us to jump back and forth between the abstraction layer and unity several times, which caused the stack corruption to occur.

  2. Resolution Note (fix version 6000.1.0b9):

    Fixes a stack corruption on SweepTestAll when doing a sweep test on a higher number than 32 colliders in a scene. Also replaced any allocators which use alloca to avoid any potential null expection crashes on IOS. We now allocate the returned hit results in one instance, instead of in a block based manner, which caused us to jump back and forth between the abstraction layer and unity several times, which caused the stack corruption to occur.

  3. Resolution Note (fix version 6000.0.42f1):

    Fixes a stack corruption on SweepTestAll when doing a sweep test on a higher number than 32 colliders in a scene. Also replaced any allocators which use alloca to avoid any potential null expection crashes on IOS. We now allocate the returned hit results in one instance, instead of in a block based manner, which caused us to jump back and forth between the abstraction layer and unity several times, which caused the stack corruption to occur.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.