Bug 35492 - Native crash arm64 ABI
Summary: Native crash arm64 ABI
Status: CONFIRMED
Alias: None
Product: Runtime
Classification: Mono
Component: JIT (show other bugs)
Version: 4.0.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Zoltan Varga
URL:
Depends on:
Blocks:
 
Reported: 2015-11-03 06:47 UTC by Przemysław Raciborski
Modified: 2016-07-13 21:58 UTC (History)
7 users (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 for Bug 35492 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Description Przemysław Raciborski 2015-11-03 06:47:53 UTC
My application crash on start - only on Samsung S6.
Natvie crash log from playstore

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/zeroltexx/zerolte:5.1.1/LMY47X/G925FXXU3COIA:user/release-keys'
Revision: '10'
ABI: 'arm64'
pid: 22411, tid: 22411, name: rtpl.myappname >>> com.mypackage.name <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: '* Assertion at /Users/builder/data/lanes/2185/53fce373/source/mono/mono/arch/arm64/../../../../mono-extensions/mono/arch/arm64/arm64-codegen.h:175, condition `arm_is_bl_disp (p, target)' not met
'
x0 0000000000000000 x1 000000000000578b x2 0000000000000006 x3 0000007f8784fe30
x4 0000007f8784fe30 x5 0000000000000005 x6 0000000000000001 x7 0000000000000020
x8 0000000000000083 x9 fefefefefefefeff x10 7f7f7f7f7f7f7f7f x11 0000000000000001
x12 0000000000000001 x13 0000007fc62ff07c x14 0000000000000001 x15 0000000000000001
x16 0000007f875dc610 x17 0000007f8757cbc4 x18 0000000000000000 x19 0000007f8784fe30
x20 0000007f878500e8 x21 0000007f875e2000 x22 000000000000000b x23 0000000000000006
x24 0000007f692edaa0 x25 0000000000000000 x26 0000000000000007 x27 0000007f45040210
x28 0000007f600a0e64 x29 0000007fc62ff000 x30 0000007f8753e264
sp 0000007fc62ff000 pc 0000007f8757cbcc pstate 0000000060000000

backtrace:
#00 pc 000000000005ebcc /system/lib64/libc.so (tgkill+8)
#01 pc 0000000000020260 /system/lib64/libc.so (pthread_kill+160)
#02 pc 0000000000021794 /system/lib64/libc.so (raise+28)
#03 pc 000000000001b17c /system/lib64/libc.so (abort+60)
#04 pc 00000000001d54e4 /data/app/com.mypackagename-1/lib/arm64/libmonosgen-2.0.so
Comment 1 Przemysław Raciborski 2015-11-04 05:23:37 UTC
It looks like that someone else also had such problems – I have found similar crash log on google.

http://www.pdfgeni.name/pastebin.com/697rF1m4?b=4
Comment 2 João Matos 2015-11-04 16:59:42 UTC
What version of Monodroid are you getting this crash with?
Comment 3 João Matos 2015-11-04 17:02:48 UTC
Nevermind, I figured out, you're using a release based off our "monodroid-5.1-series-android-mnc" branch.

Could you try reproducing with the Alpha channel, which right now is "Cycle 6 Preview Update – Release Candidate 1"?

I have reason to believe this has possibly been fixed on the latest release.
Comment 4 Przemysław Raciborski 2015-11-04 17:58:45 UTC
I will update application in store tomorrow using RC1 and we will ask one of our user (Samsung S6) for which application crashed to make a try.
Comment 5 Przemysław Raciborski 2015-12-07 10:38:52 UTC
Looks like problem is solved.
However I get exception now on Samsung S6 Edge only (g925f), might this be related your fix?

 System.ExecutionEngineExceptionSIGILL

  at Android.Runtime.JNIEnv.ExceptionOccurred () [0x0000f] in <filename unknown>:0 
  at Android.Runtime.AndroidEnvironment.GetExceptionForLastThrowable () [0x00000] in <filename unknown>:0 
  at Android.Runtime.JNIEnv.CallStaticObjectMethod (IntPtr jclass, IntPtr jmethod) [0x00057] in <filename unknown>:0 
  at Android.OS.Looper.MyLooper () [0x00032] in <filename unknown>:0 
  at Android.Runtime.AndroidEnvironment.GetDefaultSyncContext () [0x00006] in <filename unknown>:0 
  at System.AndroidPlatform.GetDefaultSyncContext () [0x00000] in <filename unknown>:0 
  at System.Threading.SynchronizationContext.GetThreadLocalContext () [0x00008] in <filename unknown>:0 
  at System.Threading.SynchronizationContext.get_CurrentNoFlow () [0x00019] in <filename unknown>:0 
  at System.Threading.Tasks.SynchronizationContextAwaitTaskContinuation.Run (System.Threading.Tasks.Task task, Boolean canInlineContinuationTask) [0x00006] in <filename unknown>:0 
  at System.Threading.Tasks.Task.FinishContinuations () [0x0008c] in <filename unknown>:0 
  at System.Threading.Tasks.Task.FinishStageThree () [0x00045] in <filename unknown>:0 
  at System.Threading.Tasks.Task`1[TResult].TrySetResult (System.Threading.Tasks.TResult result) [0x00058] in <filename unknown>:0 
  at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[TResult].SetResult (System.Runtime.CompilerServices.TResult result) [0x0001f] in <filename unknown>:0 
  at CashRush.Services.DataProvider.WebApiRestDataProvider+<GetResponse>d__9`1[TResult].MoveNext () [0x001e5] in <filename unknown>:0 
  at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.InvokeMoveNext (System.Object stateMachine) [0x00000] in <filename unknown>:0 
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) [0x00081] in <filename unknown>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) [0x00000] in <filename unknown>:0 
  at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.Run () [0x0003b] in <filename unknown>:0 
  at System.Threading.Tasks.AwaitTaskContinuation.InvokeAction (System.Object state) [0x00000] in <filename unknown>:0 
  at System.Threading.Tasks.AwaitTaskContinuation.RunCallback (System.Threading.ContextCallback callback, System.Object state, System.Threading.Tasks.Task& currentTask) [0x00017] in <filename unknown>:0 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <filename unknown>:0 
  at System.Threading.Tasks.AwaitTaskContinuation.<ThrowAsyncIfNecessary>m__0 (System.Object s) [0x00000] in <filename unknown>:0 
  at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context (System.Object state) [0x0000e] in <filename unknown>:0 
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) [0x00081] in <filename unknown>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) [0x00000] in <filename unknown>:0 
  at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x0002a] in <filename unknown>:0 
  at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in <filename unknown>:0 
  at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <filename unknown>:0 -
Comment 6 João Matos 2015-12-14 15:44:55 UTC
Hey Zoltan, assigning this to you since I do not have this device to repro or test against.
Comment 9 Zoltan Varga 2016-07-12 01:47:06 UTC
Please open another bug, other than the same error message, this could unrelated.