Search Issue Tracker

Fixed in 2017.1



Found in


Issue ID




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



Reproduction steps:
1. Open project attached (
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 (19)

  1. F03bc5c02425a6a6b2713d2da32a5d61?d=mm


    Jul 25, 2017 01:34

    Same problem.
    It is connected to disabling and enabling colliders.
    I am using it as a nasty hack to force physics to recognize that the collider is where it is after I move most of the scene to bring the player back to the origin. I will need to change it to some other method - I need a huge map.
    Anyway I am sure that this is due to me disabling and enabling the colliders.

    5.6.1f1 - this seems to be the latest version available.

  2. 0bff7de612667f451eb56a9d692a3a30?d=mm


    Jun 26, 2017 14:13

    I have Unity 5.6.1p1 and QA marked the issue I submitted (Case 924500) as a duplicate of this issue.

    "YANTMAY 12, 2017 10:25
    The fix will be available with 5.6.1p1 that is out in a few days from now. Anthony." - This is not fixed for me.

  3. 1ea7cd21d79153fa4f1d055ba65bed0b?d=mm


    Jun 01, 2017 13:19

    The fix will be available in 5.5, starting 5.5.4p1. Anthony.

  4. 08983a1787d7c7156807fe8973e0f081?d=mm


    May 30, 2017 00:46

    @Yant This issue makes our project very unstable. I can't upgrade to 5.6 right now. Because all assetbundle hashes are updated after upgrade. Every users have to re-download all assets.

  5. 08983a1787d7c7156807fe8973e0f081?d=mm


    May 30, 2017 00:34

    @Yant Do you have any plan to apply this fix for 5.5?

  6. 1ea7cd21d79153fa4f1d055ba65bed0b?d=mm


    May 15, 2017 11:04

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

  7. 436235f50ac4866e3e58bcbce1507663?d=mm


    May 12, 2017 16:12

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

  8. 1ea7cd21d79153fa4f1d055ba65bed0b?d=mm


    May 12, 2017 10:25

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

  9. 8dde32e4afe5792832b5e8ebbfb62793?d=mm


    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.

  10. 536ee62e0ba3764245cfd0250a189255?d=mm


    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.

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.