Bug 40718 - Often ExecutionEngineExceptions in sm-g930f - Samsung Galaxy S7
Summary: Often ExecutionEngineExceptions in sm-g930f - Samsung Galaxy S7
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2016-04-26 20:11 UTC by Przemysław Raciborski
Modified: 2016-04-26 22:31 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Przemysław Raciborski 2016-04-26 20:11:30 UTC
I often get System.ExecutionEngineException in Samsung Galaxy S7 Device (Insight logs).
Most of logged exceptions are in form of:
"System.ExecutionEngineExceptionSIGILL

null" (that has raised my curiosity - something must be wrong there as even thrown exception is... "wrong")

I thought that might be caused by user-code until I got logged one exception from SM-G930F device:

"System.ExecutionEngineExceptionSIGILL

  at MvvmCross.Droid.Views.MvxAndroidLifetimeMonitor.OnStop (Android.App.Activity activity) <0x7f3e03a660 + 0x00000> in <filename unknown>:0 
  at MvvmCross.Droid.Views.MvxActivityViewExtensions+<>c.<OnViewStop>b__7_0 (IMvxAndroidActivityLifetimeListener listener, Android.App.Activity activity) <0x7f3e03a610 + 0x0003f> in <filename unknown>:0 
  at MvvmCross.Droid.Views.MvxActivityViewExtensions.OnLifetimeEvent (IMvxAndroidView androidView, System.Action`2 report) <0x7f64cc9ca8 + 0x00043> in <filename unknown>:0 
  at MvvmCross.Droid.Views.MvxActivityViewExtensions.OnViewStop (IMvxAndroidView androidView) <0x7f3e03a4d0 + 0x000df> in <filename unknown>:0 
  at MvvmCross.Droid.Views.MvxActivityAdapter.EventSourceOnStopCalled (System.Object sender, System.EventArgs eventArgs) <0x7f3e03a398 + 0x000fb> in <filename unknown>:0 
  at (wrapper delegate-invoke) <Module>:invoke_void_object_EventArgs (object,System.EventArgs)
  at MvvmCross.Platform.Core.MvxDelegateExtensionMethods.Raise (System.EventHandler eventHandler, System.Object sender) <0x7f644d5248 + 0x00037> in <filename unknown>:0 
  at MvvmCross.Droid.Support.V7.AppCompat.MvxEventSourceAppCompatActivity.OnStop () <0x7f3e03a340 + 0x0001b> in <filename unknown>:0 
  at Android.App.Activity.n_OnStop (IntPtr jnienv, IntPtr native__this) <0x7f3e03a2e0 + 0x0003f> in <filename unknown>:0 
  at (wrapper dynamic-method) System.Object:8cf96119-672e-46e5-9a93-c4c02c52e8c2 (intptr,intptr)"

By analysing stacktrace we can see that exception was thrown in "MvvmCross.Droid.Views.MvxAndroidLifetimeMonitor.OnStop (Android.App.Activity activity) <" method.
Problem is: this method is empty ! Check: https://github.com/MvvmCross/MvvmCross/blob/3c735adc534a5df2d4730e9d58a08f7863c30cee/MvvmCross/Droid/Droid/Views/MvxAndroidLifeTimeMonitor.cs
 I think there is a bug in Mono compiler.
Comment 1 Przemysław Raciborski 2016-04-26 20:23:32 UTC
btw. Application was built with Xamarin.Android 6.1.0.37 (beta channel)
Comment 2 Przemysław Raciborski 2016-04-26 20:25:35 UTC
btw part2: Built Application don't use AOT compiler, APK which crashed was targeting all possible CPU/Abis.
Comment 3 Jonathan Pryor 2016-04-26 22:31:10 UTC
This is probably a dupe of Bug #40239, and should be fixed in the next cycle 7 release.