Search Issue Tracker

Fixed in Unity 2017.1

Votes

21

Found in

5.5.0p4

Issue ID

878740

Regression

Yes

Crash in physx::PxsBroadPhaseContextSap::batchUpdate after indeterminate time in play mode

Physics

-

-

Priority: 2Necessary for shipping a final release

-

Severity: 1Crash or major loss of functionality

Reproduction steps:
1. Open project attached (GoIPhysXCrashRepro.zip)
2. Open scene crashtest1.
3. Press play.
4. Wait for 1-3 minutes.

Expected result: Unity will keep working.
Actual result: Unity crashes.

Notes: It might be related to object creation/destruction but it is not totally clear which kinds of objects will trigger it and which will not.

Reproduced on: 5.5.0f3, 5.5.0p4, 5.5.1p3, 5.6.0b7.
Works fine on: 5.5.0b11.
Regression introduced in: 5.5.0f1

Comments (14)

  1. 1ea7cd21d79153fa4f1d055ba65bed0b?d=mm

    yant

    May 15, 2017 11:04

    @ AFRISBYMAY - please comment on the cloth-related cases directly. I need to know which ones exactly.

  2. 436235f50ac4866e3e58bcbce1507663?d=mm

    AFrisby

    May 12, 2017 16:12

    @Yant: will those fixes also cover the other physics crashes, e.g. the ones coming reliably from cloth physics?

  3. 1ea7cd21d79153fa4f1d055ba65bed0b?d=mm

    yant

    May 12, 2017 10:25

    The fix will be available with 5.6.1p1 that is out in a few days from now. Anthony.

  4. 8dde32e4afe5792832b5e8ebbfb62793?d=mm

    MarkoDefiant

    Apr 28, 2017 03:42

    Since the latest round of patches (April 25 & 27) didn't include this fix here's some info that might help out anyone else that is also having this issue;

    For us using 5.5.2p2 (or 5.5.2p3) and getting rid of all negative scales on rigidbodies (and their parents) seems to be avoiding this issue. It was a combination of negative scales and reparenting (along with enabling / disabling) that seemed to be the cause of the issue for us.

  5. 536ee62e0ba3764245cfd0250a189255?d=mm

    Rao-Dao-Zao

    Apr 25, 2017 18:24

    +1 to a fix for this being applied to 5.6, I have recently started experiencing it in my project but am having trouble debugging further. It would be good if Unity could at least catch the error and indicate what object(s) are problematic, but as it stands I can't get a solid repro myself to find out what I've done to cause it.

  6. B40c650a9239728009dcafa9991606b5?d=mm

    blueteak

    Apr 11, 2017 05:29

    A fix for 5.6/5.5 would be quite helpful. Seems like to big of an issue to delay for a full release cycle...

  7. 13b5ba1cf36d8854f9b71840e2a3c239?d=mm

    shaileshprabhu

    Apr 10, 2017 10:02

    Would really appreciate a patch in 5.5 or 5.6 (not sure there will be any for 5.6)? It is breaking our game for a really long time with constant crashes.

  8. 8dde32e4afe5792832b5e8ebbfb62793?d=mm

    MarkoDefiant

    Apr 10, 2017 07:28

    Can we get this fix in one of the 5.5 patches or final releases asap? Right now there is no 5.5 build that is suitable for ship; it's really messing with our deliverables.

  9. 08983a1787d7c7156807fe8973e0f081?d=mm

    Pickyguy

    Apr 10, 2017 07:11

    Not in 5.5.3p1 yet? When does it apply to 5.5.X?

  10. 1ea7cd21d79153fa4f1d055ba65bed0b?d=mm

    yant

    Mar 27, 2017 20:13

    This is to update everyone that we have a fix for this issue. Now figuring out the specifics of delivering it to you shortly. Anthony.

All about bugs

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