Your correct, my process is 1747. Don't have the full log any more (just the relevant bits to this crash).
I've also set a simple app to run the rotation_vector sensor and display the results to see if it is running the sensor that is doing it or if it is something coming from running in monogame (memory leak, starting too many threads etc) and this crash only happens when something is resource starved. George On Thu, 25 Apr 2013 11:42:35, Jonathan Pryor <[email protected]> wrote: On Apr 25, 2013, at 10:30 AM, George Banfill (Linknode Ltd) <[email protected]> wrote: > F/libc ( 393): Fatal signal 4 (SIGILL) at 0x70da0d10 (code=1), thread 407 > (SensorService) > I/DEBUG ( 125): *** *** *** *** *** *** *** *** *** *** *** *** *** *** > *** *** > I/DEBUG ( 125): Build fingerprint: > 'google/mantaray/manta:4.2.2/JDQ39/573038:user/release-keys' > I/DEBUG ( 125): Revision: '8' > I/DEBUG ( 125): pid: 393, tid: 407, name: SensorService >>> system_server > <<< > I/DEBUG ( 125): signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 70da0d10 What's are processes 393 and 125? Specifically are either _your_ process? http://docs.xamarin.com/guides/android/deployment%2C_testing%2C_and_metrics/android_debug_log#4.interesting-messages I'm going to guess that neither are your process, which means there's not anything you can do about it per-se; it look like an OS bug. Now, it's plausible that your app is doing something to trigger the OS bug, which means you'll need to possibly insert some trace messages, re-run, and see what your app is doing (if anything) before the device crashes and reboots. - Jon _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
