Crash related to PhysX (bug in PhysX 3.4)

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)

 

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:

 

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.

 

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.

 

Resurrecting this thread - have same crashes in Unity 2019.3.0b1 visible in Unity Cloud Diagnostics.

 

I am also interested in knowing why this happens.

 

> ```csharp
> Caught fatal signal - signo:11 code:1 errno:0 addr:0x6c
> Obtained 15 stack frames.
> #0 0x007f42955c0d91 in physx:xsNphaseImplementationContext::unregisterContactManager(physx:xsContactManager*)
> #1 0x007f4295562e95 in physx::Sc::Scene::finishBroadPhaseStage2(unsigned int)
> #2 0x007f4295563028 in physx::Sc::Scene::updateCCDSinglePassStage3(physx:xBaseTask*)
> #3 0x007f4295533564 in physx::Cm::Task::run()
> #4 0x007f4294af629a in PhysxJobFunc(physx:xBaseTask*)
> #5 0x007f4294a17579 in JobQueue::Exec(JobInfo*, long long, int)
> #6 0x007f4294a17704 in JobQueue::ExecuteOneJob()
> #7 0x007f4294b1dbc0 in CompletionTask:rocessAllPhysicsTasks()
> #8 0x007f4294af1b97 in PhysicsManager::Simulate(int, float)
> #9 0x007f4294a62d3e in ExecutePlayerLoop(NativePlayerLoopSystem*)
> #10 0x007f4294a62d81 in ExecutePlayerLoop(NativePlayerLoopSystem*)
> #11 0x007f4294a6329a in PlayerLoop()
> #12 0x007f4294bc686e in PlayerMain(int, char**)
> #13 0x007f4293590b97 in __libc_start_main
> #14 0x00558574610689 in _start
> ```
My server shuts down itself after this error occurs.

 

I don't know why it posted the code in emoji format? it's supposed to be double : I guess anything with "" results in emoji?

 

Which version of Unity are you using?

 

constant physx crashes here too, only when im using navagents, any solution? unity is buggier than ever these days