Search Unity

  1. Unity 2019.2 is now released.
    Dismiss Notice

Crash related to PhysX (bug in PhysX 3.4)

Discussion in 'Physics' started by Sailendu, Jun 26, 2019.

  1. Sailendu

    Sailendu

    Joined:
    Jul 23, 2009
    Posts:
    144
    Hello,

    I have so many of these similar crash reports in Unity analytics dashboard, but can not understand where the crash is happening. Can anyone please help with this Native StackTrace? I am using Unity 2019.1.8 and Android build with IL2CPP and also uploaded the symbol file to the analytics dashboard. But there are some symbol missing in the stack trace. I can not understand how to find where the crash is happening. The Logs tab in the report also does not contain any error. Please help.

    Iin line 4, 5, 6, 7 it is something related to physx. I don't see any crash in any of my devices. These are only on Unity Analytics, there are also so many crashes in Google Play Console, but those reports are even more hard to understand as those contains only some numbers. Somebody please help me.

    The report title is:
    Native Crash - CrashReporting::Android::SignalHandler(int, siginfo*, void*) (Unknown File)

     
  2. Sailendu

    Sailendu

    Joined:
    Jul 23, 2009
    Posts:
    144
    The crash reports in Unity Analytics and Google Play Console are so different, the crashes in Unity analytics are mostly about physx but in play console the crashes don't have much information (see the report below). And the crashes in unity analytics are all in android os version 4.4.4 but in play console mostly android os version 8.1 and 8.0. So I don't understand how crashes don't match. It means analytics crashes are not in play console and vise versa. Someone please help.

    Google Play report:
     
    xwwwwwunity likes this.
  3. Sailendu

    Sailendu

    Joined:
    Jul 23, 2009
    Posts:
    144
    I found a crash issue reported in the nvidia physx github which is related to this crash in Unity I mentioned in the first post, the same function
    PxsNphaseImplementationContext::unregisterContactManager.
    The guys from nvidia said there is a bug in physx version 3.4 which is the new physx version in Unity. And they posted some fix in the thread link below:
    https://github.com/NVIDIAGameWorks/PhysX/issues/48

    Please have a look at the link, and as it is a bug in physx engine itself we can not fix it in script. It really needs to be fixed as it it causing so many crashes.
     
  4. Sailendu

    Sailendu

    Joined:
    Jul 23, 2009
    Posts:
    144
    Is there anybody from Unity looking at this? This is a big issue because the crash bug is in the PhysX engine version 3.4 inside Unity. Please somebody from Unity look into the issue. You can check the bug in official PhysX forum link in the previous post.
     
  5. Revolter

    Revolter

    Joined:
    Mar 15, 2014
    Posts:
    110
    Resurrecting this thread - have same crashes in Unity 2019.3.0b1 visible in Unity Cloud Diagnostics.

    upload_2019-9-2_20-46-47.png
    upload_2019-9-2_20-47-8.png
    upload_2019-9-2_20-47-24.png
     

    Attached Files:

  6. Nyanpas

    Nyanpas

    Joined:
    Dec 29, 2016
    Posts:
    83
    I am also interested in knowing why this happens.