Unity 5.3 Crash Samsung Only

Hi guys, I posted another thread, in the wrong forum, but got some of the details wrong.

After upgrading from Unity 5.1.4f1 to Unity 5.3.1 - and then to p1 and p2 - I'm getting a crash on device. It happens our Samsung Galaxy Note 10.1 which is running Android 4.4.2. The crash happens seemingly at random, I can't reproduce it reliably, it just happens after playing for a while.

The only code changes between the Unity 5.1.4f1 build and the Unity 5.3.1p2 are changes to accommodate for the new SceneManager in Unity 5.3.

The game does not crash on a Nexus 7 (2013) running Android 6.0, or on an NVIDIA Shield running 5.1.1.
It crashes on both Development and non-Development builds. Both with and without WiFi connectivity.

I have attached a log file from one of the crashes. It contains tombstone data, I'm not sure what to do with this, I've gleaned all I can from it. I'm not an Android developer so I don't know much when it gets over to native code.

Any help would be much appreciated.

 

According to my (limited) knowledge in analyzing these native crashes, it looks like the crash came from libmono (the Mono runtime that Unity uses).

Since the issue occurs only on a Samsung device that may be related... Maybe @Yury Habets or @bitter can further comment on what can be done to better analyze such crashes ?

One thing that came to mind is that perhaps, if the crash occurs in the Mono runtime, maybe there are some debug "flags" that can be used to get more information about crashes in Mono... not sure such exist, but worth checking

 

What sort of a debugger should be used for diagnosing native crashes? also, are you aware of a "debug" version of the Mono runtime (or a flag) that can be used ?

 

As @liortal asked, how would I go about debugging this?

The bug is reproed randomly, but it has usually happened after about half an hour (timing varies drastically).
I'll try and strip things out of the project, but it's a huge project, and most things are dependant on each other.