Xamarin-android: "Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)" native fault during C# exception handling on ARM64 devices

Created on 22 May 2019 · 49Comments · Source: xamarin/xamarin-android

Steps to Reproduce

Debug app on device
App deploys
App tries to launch but crashes immediately

Expected Behavior

No crash

Actual Behavior

App crashes immediately when trying to debug on target device.

Version Information

Microsoft Visual Studio Enterprise 2019
Version 16.1.0
VisualStudio.16.Release/16.1.0+28917.181
Microsoft .NET Framework
Version 4.7.03190

Installed Version: Enterprise

Visual C++ 2019   00435-60000-00000-AA300
Microsoft Visual C++ 2019

ADL Tools Service Provider   1.0
This package contains services used by Data Lake tools

Application Insights Tools for Visual Studio Package   9.1.00429.1
Application Insights Tools for Visual Studio

ASP.NET and Web Tools 2019   16.1.429.50124
ASP.NET and Web Tools 2019

ASP.NET Web Frameworks and Tools 2019   16.1.429.50124
For additional information, visit https://www.asp.net/

Azure App Service Tools v3.0.0   16.1.429.50124
Azure App Service Tools v3.0.0

Azure Data Lake Node   1.0
This package contains the Data Lake integration nodes for Server Explorer.

Azure Data Lake Tools for Visual Studio   2.3.9000.0
Microsoft Azure Data Lake Tools for Visual Studio

Azure Functions and Web Jobs Tools   16.1.429.50124
Azure Functions and Web Jobs Tools

Azure Stream Analytics Tools for Visual Studio   2.3.9000.0
Microsoft Azure Stream Analytics Tools for Visual Studio

C# Tools   3.1.0-beta4-19266-03+9d80dea7fe1b14043b9b2ac4d0b59ed26f508742
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Common Azure Tools   1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

Extensibility Message Bus   1.1.77 (master@24013d5)
Provides common messaging-based MEF services for loosely coupled Visual Studio extension components communication and integration.

Fabric.DiagnosticEvents   1.0
Fabric Diagnostic Events

IntelliCode Extension   1.0
IntelliCode Visual Studio Extension Detailed Info

JetBrains ReSharper Ultimate 2019.1.1   Build 191.0.20190501.122851
JetBrains ReSharper Ultimate package for Microsoft Visual Studio. For more information about ReSharper Ultimate, visit http://www.jetbrains.com/resharper. Copyright © 2019 JetBrains, Inc.

Microsoft Azure HDInsight Azure Node   2.3.9000.0
HDInsight Node under Azure Node

Microsoft Azure Hive Query Language Service   2.3.9000.0
Language service for Hive query

Microsoft Azure Service Fabric Tools for Visual Studio   2.5
Microsoft Azure Service Fabric Tools for Visual Studio

Microsoft Azure Stream Analytics Language Service   2.3.9000.0
Language service for Azure Stream Analytics

Microsoft Azure Stream Analytics Node   1.0
Azure Stream Analytics Node under Azure Node

Microsoft Azure Tools   2.9
Microsoft Azure Tools for Microsoft Visual Studio 0x10 - v2.9.20419.2

Microsoft Continuous Delivery Tools for Visual Studio   0.4
Simplifying the configuration of Azure DevOps pipelines from within the Visual Studio IDE.

Microsoft JVM Debugger   1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

Microsoft Library Manager   1.0
Install client-side libraries easily to any web project

Microsoft MI-Based Debugger   1.0
Provides support for connecting Visual Studio to MI compatible debuggers

Microsoft Visual C++ Wizards   1.0
Microsoft Visual C++ Wizards

Microsoft Visual Studio Tools for Containers   1.1
Develop, run, validate your ASP.NET Core applications in the target environment. F5 your application directly into a container with debugging, or CTRL + F5 to edit & refresh your app without having to rebuild the container.

Microsoft Visual Studio VC Package   1.0
Microsoft Visual Studio VC Package

Mono Debugging for Visual Studio   16.1.1 (2473f22)
Support for debugging Mono processes with Visual Studio.

NuGet Package Manager   5.1.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/

ProjectServicesPackage Extension   1.0
ProjectServicesPackage Visual Studio Extension Detailed Info

ResourcePackage Extension   1.0
ResourcePackage Visual Studio Extension Detailed Info

ResourcePackage Extension   1.0
ResourcePackage Visual Studio Extension Detailed Info

Snapshot Debugging Extension   1.0
Snapshot Debugging Visual Studio Extension Detailed Info

SQL Server Data Tools   16.0.61904.23160
Microsoft SQL Server Data Tools

ToolWindowHostedEditor   1.0
Hosting json editor into a tool window

TypeScript Tools   16.0.10506.2004
TypeScript Tools for Microsoft Visual Studio

Visual Basic Tools   3.1.0-beta4-19266-03+9d80dea7fe1b14043b9b2ac4d0b59ed26f508742
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Visual F# Tools 10.4 for F# 4.6   16.1.0-beta.19253.3+42526fe359672a05fd562dc16a91a43d0fe047a7
Microsoft Visual F# Tools 10.4 for F# 4.6

Visual Studio Code Debug Adapter Host Package   1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio

Visual Studio Tools for Containers   1.0
Visual Studio Tools for Containers

Visual Studio Tools for Kubernetes   1.0
Visual Studio Tools for Kubernetes

VisualStudio.Mac   1.0
Mac Extension for Visual Studio

Xamarin   16.1.0.542 (d16-1@68b985244)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin Designer   16.1.0.418 (remotes/origin/d16-1@5b958bb10)
Visual Studio extension to enable Xamarin Designer tools in Visual Studio.

Xamarin Templates   16.2.112 (4db4af4)
Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.

Xamarin.Android SDK   9.3.0.22 (HEAD/8e7764fdf)
Xamarin.Android Reference Assemblies and MSBuild support.
    Mono: mono/mono/2018-08@3cb36842fc4
    Java.Interop: xamarin/java.interop/d16-1@5ddc3e3
    LibZipSharp: grendello/LibZipSharp/d16-1@44de300
    LibZip: nih-at/libzip/rel-1-5-1@b95cf3f
    ProGuard: xamarin/proguard/master@905836d
    SQLite: xamarin/sqlite/3.27.1@8212a2d
    Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-1@acabd26


Xamarin.iOS and Xamarin.Mac SDK   12.10.0.153 (750a879)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.

Log File


=================================================================
    Native Crash Reporting
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

=================================================================
    Basic Fault Adddress Reporting05-22 15:17:13.732 E/mono-rt (18283): /proc/self/maps:

=================================================================
Memory around native instruction pointer (0x7d29637678):0x7d29637668  00 1c 40 b9 c0 03 5f d6 fd 7b bf a9 fd 03 00 91  ..@..._..{......
0x7d29637678  08 20 40 b9 a8 00 c8 37 88 01 e0 37 00 00 40 f9  05-22 15:17:13.732 E/mono-rt (18283): 12c00000-12d40000 rw-p 00000000 00:01 19702                              /dev/ashmem/dalvik-main space (region space) (deleted)

. @....7...7..@.
0x7d29637688  fd 7b c1 a8 c0 03 5f d6 60 08 00 b0 01 0a 00 f0  .{...._.`.......
0x7d29637698  03 0a 00 f0 00 24 06 91 21 80 08 91 63 8c 0a 91  .....$..!...c...

No native Android stacktrace (see debuggerd output).

=================================================================
    Managed Stacktrace:
=================================================================
      at <unknown> <0xffffffff>
      at WP1_Tablet.Shared.App:.ctor <0x00087>
      at WP1_Tablet.Droid.MainActivity:OnCreate <0x008a3>
      at Android.App.Activity:n_OnCreate_Landroid_os_Bundle_ <0x000ef>
      at Android.Runtime.DynamicMethodNameCounter:7 <0x00027>
      at Android.Runtime.DynamicMethodNameCounter:7 <0x000cf>
=================================================================05-22 15:17:13.732 E/mono-rt (18283): 12d40000-1b500000 ---p 00140000 00:01 19702                              /dev/ashmem/dalvik-main space (region space) (deleted)

05-22 15:17:13.732 E/mono-rt (18283): 1b500000-1b7c0000 ---p 08900000 00:01 19702                              /dev/ashmem/dalvik-main space (region space) (deleted)
05-22 15:17:13.732 E/mono-rt (18283): 1b7c0000-1b800000 rw-p 08bc0000 00:01 19702                              /dev/ashmem/dalvik-main space (region space) (deleted)
05-22 15:17:13.732 E/mono-rt (18283): 1b800000-1e0c0000 ---p 08c00000 00:01 19702                              /dev/ashmem/dalvik-main space (region space) (deleted)
05-22 15:17:13.732 E/mono-rt (18283): 1e0c0000-52c00000 rw-p 0b4c0000 00:01 19702                              /dev/ashmem/dalvik-main space (region space) (deleted)
05-22 15:17:13.732 E/mono-rt (18283): 70b7d000-70b92000 rw-p 00000000 fd:01 442539                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 70b92000-70b93000 rw-p 00000000 fd:01 442542                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 70b93000-70b95000 rw-p 00000000 fd:01 442543                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 70b95000-70dc3000 rw-p 00000000 fd:01 442546                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 70dc3000-70e88000 rw-p 00000000 fd:01 442551                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 70e88000-70ed2000 rw-p 00000000 fd:01 442555                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 70ed2000-70efe000 rw-p 00000000 fd:01 442557                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 70efe000-70f2f000 rw-p 00000000 fd:01 442558                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 70f2f000-70f3f000 rw-p 00000000 fd:01 442559                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 70f3f000-70f44000 rw-p 00000000 fd:01 442560                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 70f44000-70f6f000 rw-p 00000000 fd:01 442561                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 70f6f000-71568000 rw-p 00000000 fd:01 442562                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 71568000-715ac000 rw-p 00000000 fd:01 442563                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 715ac000-715b7000 rw-p 00000000 fd:01 442564                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 715b7000-715c2000 rw-p 00000000 fd:01 442565                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 715c2000-715e8000 rw-p 00000000 fd:01 442566                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 715e8000-715ea000 rw-p 00000000 fd:01 442567                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 715ea000-715ed000 rw-p 00000000 fd:01 442568                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.732 E/mono-rt (18283): 715ed000-715ee000 rw-p 00000000 fd:01 442569                             /data/dalvik-cache/arm64/system@[email protected]
05-22 15:17:13.748 F/libc    (18283): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 18283 (_Tablet.Android), pid 18283 (_Tablet.Android)

VS bug #897846

Mono runtime or AOT Compiler bug high-priority regression

Source

darkblackcorner

Most helpful comment

Candidate development installer packages that include the fix:

Xamarin.Android.Sdk.9.3.0.23.vsix for Windows
xamarin.android-9.3.0-23.pkg for macOS (for users on the Preview channel of Visual Studio for Mac)

I did a quick sanity check of these packages to verify that I could run a couple of the test cases successfully. That said, note that these are not fully validated packages. They should be considered experimental for now until they have been published as part of Visual Studio.

Installing and uninstalling these experimental packages

For either installer, ensure that the file downloads with the correct extension, and then double-click it to install. When running the .vsix installer on Windows, be sure to select only Visual Studio 2019 if you have multiple versions of Visual Studio installed.

When this Xamarin.Android package is installed, Visual Studio for Mac will offer to downgrade back to version Xamarin.Android SDK version 9.3.0.22, so you will need to ignore that update to keep using this experimental version, until the newer Xamarin.Android version is published to the Visual Studio for Mac updater channel. On the other hand, if you wish to revert to Xamarin.Android SDK version 9.3.0.22 after trying the experimental package, then you can apply the older version from the updater.

If you wish to revert to Xamarin.Android SDK version 9.3.0.22 in Visual Studio on Windows, navigate to Extensions > Manage Extensions, select the Xamarin.Android SDK entry, and click Revert.

brendanzagaeski on 11 Jun 2019

👍10 🎉2

All 49 comments

This looks like it could be a regression of https://github.com/xamarin/xamarin-android/issues/2920?

darkblackcorner on 22 May 2019

Thanks for the report! As a next step, if you get a chance, if you can repeat the app crash once more and collect the adb logcat -d output, that would be excellent:

Open Tools > Android > Android Adb Command Prompt.
Run the following command to clear the log on the device:
```
adb logcat -c
```
Repeat the app crash once more.
Run the following command to collect the log from the device:
```
adb logcat -d > "%USERPROFILE%\Desktop\adblogcat.txt"
```
Attach back the adblogcat.txt file from your desktop, or if you prefer, copy and paste just the section of it that starts with the "E/mono-rt" lines you included in the original description and ends after the section that starts with a "Build fingerprint:" line and includes a "backtrace:" section (the native backtrace).

The additional "backtrace:" information will often contain the name of the native function where the app exited unexpectedly, which can be helpful to distinguish among different native crashes.

(I have an initial suspicion that the scope of https://github.com/mono/mono/issues/14170 might be larger than it initially appeared. That problem might be causing unexpected exits when debugging in more circumstances than just when continuing through an unhandled exception. The additional information from the "backtrace:" should hopefully provide an additional clue to confirm that idea or indicate that there is another separate problem involving native aborts.)

Thanks in advance!

brendanzagaeski on 22 May 2019

It didn't crash immediately this time, but didn't take long.
I also tried with an empty project, but unable to reproduce that way.
adblogcat.txt

darkblackcorner on 23 May 2019

Hi @brendanzagaeski, thanks for looking at this.

@darkblackcorner and I are actually working on the same project. I have done some additional testing on this issue and found that the issue only occurs on one of my devices (a Panasonic FZ-N1 MK2 - API Level 27). It happens regardless if the app is launched with the debugger or not. I have a feeling that this issue is specific to the arm64-v8a architecture, as that seems to be the common denominator between my log and @darkblackcorner. I have attached my log as well, mine still crashed immediately. I'll be interested to learn what you find.

Thanks again.

adblogcat_EP01.txt

EP01 on 23 May 2019

Confirmed the issue is not present on the same device using the armeabi-v7a ABI.

EP01 on 23 May 2019

I am having a very similar issue since the last VS19 update when using EntityFrameworkCore.Sqlite in my app. The app crashes with a similar (or same) error as above (SIGSEGV). More specifically, creating the database with Migrate() caused the crash and I was able to work around it by providing an empty database where EF7 expects it before the Migrate() call. However, this didn't solve the problem completely and the app is still crashing on some of my users devices.

I can also confirm that it doesn't crash with arm64-v8adisabled when debugging, but still crashes with armeabi-v7aat Release-mode.

If needed, I can provide a solution to reproduce the problem

tipa on 23 May 2019

Log & sample project:
adblogcat.txt
App1.zip

tipa on 23 May 2019

Thanks much for the quick replies, log files, and test case! At first glance, it looks like the suspicion that this has the same root cause as https://github.com/mono/mono/issues/14170 might be right. The mono_jit_info_get_method+8 native fault location from that issue is also appearing in the "backtrace" section of these new log files:

backtrace:
    #00 pc 0000000000177678  /data/app/Mono.Android.DebugRuntime-oFKYupVsEWJ0Dq7bXjLmiA==/lib/arm64/libmonosgen-64bit-2.0.so (mono_jit_info_get_method+8)
    #01 pc 00000000000be654  /data/app/Mono.Android.DebugRuntime-oFKYupVsEWJ0Dq7bXjLmiA==/lib/arm64/libmonosgen-64bit-2.0.so

I'll do one more quick confirmation with the test app tipa just provided to grab the backtrace with debug symbols added, and then I'll escalate the issue with the runtime and debugger engineers.

brendanzagaeski on 23 May 2019

Thanks again for the test case! The backtrace with symbols does indeed also match https://github.com/mono/mono/issues/14170:

  * frame #0: 0x0000007126cf5da8 libart.so`art_sigsegv_fault
    frame #1: 0x0000007126cf62b4 libart.so`art::FaultManager::HandleFault(int, siginfo*, void*) + 356
    frame #2: 0x00000058b5382b5c app_process64`___lldb_unnamed_symbol20$$app_process64 + 572
    frame #3: 0x00000071acbdd870 [vdso]
    frame #4: 0x00000071107d1640 libmonosgen-2.0.d.so`mono_handle_exception_internal [inlined] jinfo_get_method(ji=0x0000000000000000) at mini-runtime.h:390
    frame #5: 0x00000071107d1638 libmonosgen-2.0.d.so`mono_handle_exception_internal(ctx=<unavailable>, obj=<unavailable>, resume=0, out_ji=<unavailable>) at mini-exceptions.c:2701
    frame #6: 0x00000071107d1640 libmonosgen-2.0.d.so`mono_handle_exception_internal [inlined] jinfo_get_method(ji=0x0000007108452a58) at mini-runtime.h:390
    frame #7: 0x00000071107d1638 libmonosgen-2.0.d.so`mono_handle_exception_internal(ctx=<unavailable>, obj=<unavailable>, resume=0, out_ji=<unavailable>) at mini-exceptions.c:2701
    frame #8: 0x00000071107d12b8 libmonosgen-2.0.d.so`mono_handle_exception(ctx=<unavailable>, obj=<unavailable>) at mini-exceptions.c:2988
    frame #9: 0x000000711080901c libmonosgen-2.0.d.so`mono_arm_throw_exception(arg=<unavailable>, pc=<unavailable>, int_regs=0x0000007fcd282870, fp_regs=0x0000007fcd282970, corlib=<unavailable>, rethrow=1) at exceptions-arm64.c:410

It looks like certain re-thrown exceptions are sufficient to cause this problem even if they are caught and handled within an external library. In this case, it looks like the exception that's triggering the native fault might be a Microsoft.Data.Sqlite.SqliteException that is thrown from Microsoft.Data.Sqlite.dll, and then re-thrown from Microsoft.EntityFrameworkCore.Relational.dll. If I set the debugger to break on all thrown exceptions, I can break on the original thrown exception and the re-thrown exception, but the app aborts after I then continue through the re-thrown exception.

I will escalate this with the runtime and debugger engineers.

For the runtime and debugger engineers, in case it might be helpful, here's a slightly adjusted test case to make the sqlite call happen on a button tap so that it's easier to attach the native debugger before the crash:

RethrownExceptionCrash.zip

brendanzagaeski on 23 May 2019

Probably related, also this simple 2-liner crashes in a similar fashion:

try { throw new FileLoadException(); }
catch (System.Exception e) when (e is FileLoadException) { }

tipa on 23 May 2019

https://github.com/xamarin/Xamarin.Forms/issues/6269

thudugala on 23 May 2019

Additional notes for the runtime and debugger engineers:

I tested a number of the Xamarin.Android continuous development builds to attempt to narrow down the range of commits involved in this change in behavior. Long story short, the commit that introduced the problem was https://github.com/xamarin/xamarin-android/commit/06e920c18b71a165eded0a5782f1a285ef20a4bc, which updated the product build process to use Android NDK r19 to build the Mono runtime. It seems this changed the behavior of the Mono runtime in an unexpected way. I'm not sure if the problem is most likely due to an older bug in the Mono runtime that was only exposed after the change in the Android NDK or if the newer Android NDK version itself might have a bug.

Testing details

Good Behavior

Build tested: https://jenkins.xamarin.com/view/Xamarin.Android/job/xamarin-android-freestyle/1432/Azure/
Corresponding commit: https://github.com/xamarin/xamarin-android/commit/76fb90e03194d5999c4da3b0146da40eca257295

Behavior of the re-thrown exception test case from earlier in this issue

Runs without error.

(Note that once this app runs once successfully, it will not show the error again for another version of the Mono runtime unless the application data is cleared, presumably because the SQLite database does not need to be created again once it exists in the application data directory.)

Behavior of the filtered exception test case from the linked Xamarin.Forms issue

Continues running successfully after the TRY EXCEPTION button has been tapped.

Problematic Behavior

Build tested: https://jenkins.xamarin.com/view/Xamarin.Android/job/xamarin-android-freestyle/1436/
Corresponding commit: https://github.com/xamarin/xamarin-android/commit/06e920c18b71a165eded0a5782f1a285ef20a4bc

Behavior of the re-thrown exception test case from earlier in this issue

The application crashes:

* thread #1, name = 'ompanyname.App1', stop reason = breakpoint 1.1
  * frame #0: 0x0000007126cf5da8 libart.so`art_sigsegv_fault
    frame #1: 0x0000007126cf62b4 libart.so`art::FaultManager::HandleFault(int, siginfo*, void*) + 356
    frame #2: 0x00000058b5382b5c app_process64`___lldb_unnamed_symbol20$$app_process64 + 572
    frame #3: 0x00000071acbdd870 [vdso]
    frame #4: 0x00000071107c05e8 libmonosgen-2.0.d.so`mono_handle_exception_internal [inlined] jinfo_get_method(ji=0x0000000000000000) at mini-runtime.h:390
    frame #5: 0x00000071107c05e0 libmonosgen-2.0.d.so`mono_handle_exception_internal(ctx=<unavailable>, obj=<unavailable>, resume=0, out_ji=<unavailable>) at mini-exceptions.c:2630
    frame #6: 0x00000071107c05e8 libmonosgen-2.0.d.so`mono_handle_exception_internal [inlined] jinfo_get_method(ji=0x0000007109695998) at mini-runtime.h:390
    frame #7: 0x00000071107c05e0 libmonosgen-2.0.d.so`mono_handle_exception_internal(ctx=<unavailable>, obj=<unavailable>, resume=0, out_ji=<unavailable>) at mini-exceptions.c:2630
    frame #8: 0x00000071107c0260 libmonosgen-2.0.d.so`mono_handle_exception(ctx=<unavailable>, obj=<unavailable>) at mini-exceptions.c:2917
    frame #9: 0x00000071107f7ed0 libmonosgen-2.0.d.so`mono_arm_throw_exception(arg=<unavailable>, pc=<unavailable>, int_regs=0x0000007fcd2831f0, fp_regs=0x0000007fcd2832f0, corlib=<unavailable>, rethrow=1) at exceptions-arm64.c:410

Behavior of the filtered exception test case from the linked Xamarin.Forms issue

The application crashes:

* thread #1, name = 'com.companyname', stop reason = breakpoint 1.1
  * frame #0: 0x0000007126cf5da8 libart.so`art_sigsegv_fault
    frame #1: 0x0000007126cf62b4 libart.so`art::FaultManager::HandleFault(int, siginfo*, void*) + 356
    frame #2: 0x00000058b5382b5c app_process64`___lldb_unnamed_symbol20$$app_process64 + 572
    frame #3: 0x00000071acbdd870 [vdso]
    frame #4: 0x000000711014f5e8 libmonosgen-2.0.d.so`mono_handle_exception_internal [inlined] jinfo_get_method(ji=0x0000000000000000) at mini-runtime.h:390
    frame #5: 0x000000711014f5e0 libmonosgen-2.0.d.so`mono_handle_exception_internal(ctx=<unavailable>, obj=<unavailable>, resume=0, out_ji=<unavailable>) at mini-exceptions.c:2630
    frame #6: 0x000000711014f5e8 libmonosgen-2.0.d.so`mono_handle_exception_internal [inlined] jinfo_get_method(ji=0x000000710ab23aa0) at mini-runtime.h:390
    frame #7: 0x000000711014f5e0 libmonosgen-2.0.d.so`mono_handle_exception_internal(ctx=<unavailable>, obj=<unavailable>, resume=0, out_ji=<unavailable>) at mini-exceptions.c:2630
    frame #8: 0x000000711014f260 libmonosgen-2.0.d.so`mono_handle_exception(ctx=<unavailable>, obj=<unavailable>) at mini-exceptions.c:2917
    frame #9: 0x0000007110186ed0 libmonosgen-2.0.d.so`mono_arm_throw_exception(arg=<unavailable>, pc=<unavailable>, int_regs=0x0000007fcd2833b0, fp_regs=0x0000007fcd2834b0, corlib=<unavailable>, rethrow=0) at exceptions-arm64.c:410

(I'm omitting the results for the test case from https://github.com/mono/mono/issues/14170 for the moment because those results were different in some curious ways across the versions I tested, and that scenario isn't as important as the more common scenarios from the other user-submitted test cases.)

brendanzagaeski on 24 May 2019

Is there any workaround? Can I downgrade the VS2019 extension of xamarin android somehow?

tobiasschulz on 24 May 2019

No general workaround that covers all the affected scenarios is known at this time.

It is possible to download the .vsix installer package for the previous version of the Xamarin.Android SDK from the list on https://github.com/xamarin/xamarin-android/, but the Visual Studio Installer aims to prevent potential invalid configurations, so it does not allow installing older versions of a .vsix than is currently installed. If you open the .vsix package as a ZIP archive, for example by renaming it to have a .zip extension and browsing it in Explorer, it is possible to view the $MSBuild directory and $ReferenceAssemblies directory that make up the Xamarin.Android SDK installation. In principle you can move the following subdirectories out of the way (adjusting the paths based on your Visual Studio install location):

C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\Android
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\Xamarin.Android.Sdk.props
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\Xamarin.Android.Sdk.targets
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Novell
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\Microsoft\Framework\MonoAndroid

And then you can copy the corresponding directories and files from within the .vsix archive. This is the technique that the setup-windows.exe command in the open source development build .zip archives use. Since this is approach is intended mostly for test usage of development builds, it would be recommended to use the full previous Visual Studio installation whenever possible instead. For example, in this case, the previous version of Visual Studio 2019 would be version 16.0. The installer for that previous version can be found via a Visual Studio subscription or the Dev Essentials program, for example using the Download button for Visual Studio 2017 on https://visualstudio.microsoft.com/vs/older-downloads/ and adjusting the search from Visual Studio 2017 to Visual Studio 2019.

brendanzagaeski on 24 May 2019

No general workaround that covers all the affected scenarios is known at this time.

It is possible to download the _.vsix_ installer package for the previous version of the Xamarin.Android SDK from the list on https://github.com/xamarin/xamarin-android/, but the Visual Studio Installer aims to prevent potential invalid configurations, so it does not allow installing older versions of a _.vsix_ than is currently installed. If you open the _.vsix_ package as a ZIP archive, for example by renaming it to have a _.zip_ extension and browsing it in Explorer, it is possible to view the _$MSBuild_ directory and _$ReferenceAssemblies_ directory that make up the Xamarin.Android SDK installation. In principle you can move the following subdirectories out of the way (adjusting the paths based on your Visual Studio install location):

_C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\Android_

_C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\Xamarin.Android.Sdk.props_

_C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\Xamarin.Android.Sdk.targets_

_C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Novell_

_C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\ReferenceAssemblies\Microsoft\Framework\MonoAndroid_

And then you can copy the corresponding directories and files from within the _.vsix_ archive. This is the technique that the setup-windows.exe command in the open source development build _.zip_ archives use. Since this is approach is intended mostly for test usage of development builds, it would be recommended to use the full previous Visual Studio installation whenever possible instead. For example, in this case, the previous version of Visual Studio 2019 would be version 16.0. The installer for that previous version can be found via a Visual Studio subscription or the Dev Essentials program, for example using the Download button for Visual Studio 2017 on https://visualstudio.microsoft.com/vs/older-downloads/ and adjusting the search from Visual Studio 2017 to Visual Studio 2019.

I'm trying to download the older version, but there´s no Community Edition 16.0 in Dev Essentials Program! Only the version 16.1. :-(

mapsouza on 25 May 2019

Ooh yes, apologies. I should have mentioned that the older Visual Studio 2019 versions are only available for the Professional and higher editions. So Community editions are a scenario where using the manual directory replacement technique could indeed be the best strategy for temporary use of an older Xamarin.Android SDK version.

brendanzagaeski on 25 May 2019

@brendanzagaeski: do you have a sense of when a fix for this issue might come out? I'm dead in the water right now, and weighing the cost of downgrading to 16.0 vs. waiting.

mfeingol on 28 May 2019

👍1

I'm not too sure yet of the timeline for a release with a fix. Historically, the time between Visual Studio 2017 version 15.x.x updates was under a month, and so far the time between Visual Studio 2019 version 16.0.x updates has been at most 2 weeks. I'm definitely hoping that a fix for this issue can be included in the soonest possible 16.1.x update.

Hopefully there will be more news this week about this issue and the progress toward releasing a fix. I will keep this issue updated with anything useful I learn outside of this issue.

brendanzagaeski on 28 May 2019

😕1 👍1

Additional notes for the runtime and debugger engineers (/cc @lambdageek in case it might be useful):

At least for the test cases linked to this issue so far, I am not able to reproduce the problem when using the unpublished development builds of Xamarin.Android SDK version 9.4.0.7 or 9.4.0.17. So it's possible that one or more of the changes between mono/mono/2018-08@3cb36842fc4 and mono/mono/2018-10@904bd79d9d8 might have resolved this issue. I'm not sure if that might just be a lucky timing change or if maybe a small number of the changes could be backported to resolve the issue on the 2018-10 branch.

Version Info

Xamarin.Android SDK 9.4.0.17 (d16-2/bce1291)
Mono: mono/mono/2019-02@3dc72cfe513

Xamarin.Android SDK 9.4.0.7 (HEAD/d391eb462)
Mono: mono/mono/2018-10@904bd79d9d8

Xamarin.Android SDK 9.3.0.22 (HEAD/8e7764fdf)
Mono: mono/mono/2018-08@3cb36842fc4

(Xamarin.Android SDK version 9.4 is planned for inclusion in a future Visual Studio 2019 version 16.2 Preview release, but it hasn't been published as part of a Visual Studio preview yet.)

brendanzagaeski on 29 May 2019

Follow-up notes for the runtime and debugger engineers:

Darn. It looks like the reason the current development build of the Xamarin.Android SDK version 9.4.0.7 works is just that the Mono runtime in that version was built with the older Android NDK r14b. So the Mono changes in that version won't offer any clues about a possible fix to backport after all.

What happened is that starting in https://github.com/xamarin/xamarin-android/commit/333b98b3bf3be7bc812a615bdff48deebbd46ab4, the Xamarin.Android SDK build started consuming the version of the Mono runtime that is built separately as part of the Mono product build. Before that, the Xamarin.Android product build was building its own Mono runtime. (The open source build of 333b98b does not hit the issue, but the previous build does.) As I understand it, the Mono product build is currently using Android NDK r14b to build the Mono runtime for Android.

/cc @jonpryor for a heads-up that the Mono bundle currently being pulled in by the xamarin-android/d16-2 versions is built with Android NDK r14b. I suspect that might need to be updated before the first non-preview version of Xamarin.Android 9.4?

brendanzagaeski on 29 May 2019

No general workaround that covers all the affected scenarios is known at this time.

in my case, which you wrote is the same, i just build project with visual studio 2017. 15.9.11 , so , it may be considered as workaround (w/o downgrading VS 2019 )

ish-1313 on 30 May 2019

We encountered this problem yesterday and today. LG V30 and S9 using an ARM64 build. As soon as we configured the Android project to only support armeabi-v7a, we found a case where we were attempting to access a disposed object.

In our case the exception was wrapped by a try-catch. On ARM64 we encountered the null pointer issue.

=================================================================
    Native Crash Reporting
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

=================================================================
    Basic Fault Adddress Reporting
06-04 12:57:31.509 E/mono-rt (29535): /proc/self/maps:
=================================================================
Memory around native instruction pointer (0x740dd8d678):0x740dd8d668  00 1c 40 b9 c0 03 5f d6 fd 7b bf a9 fd 03 00 91  ..@..._..{......
0x740dd8d678  08 20 40 b9 a8 00 06-04 12:57:31.509 E/mono-rt (29535): 12c00000-52c00000 rw-p 00000000 00:01 22869                              /dev/ashmem/dalvik-main space (region space) (deleted)

06-04 12:57:31.509 E/mono-rt (29535): 70555000-707fd000 rw-p 00000000 fd:01 1032299                            /data/dalvik-cache/arm64/system@[email protected] 37 88 01 e0 37 00 00 40 f9  . @....7...7..@.
0x740dd8d688  fd 7b c1 a8 c0 03 5f d6 60 08 00 b0 01 0a 00 f0  .{...._.`.......
0x740dd8d698  03 0a 00 f0 00 24 06 91 21 80 08 91 63 8c 0a 91  .....$..!...c...

No native Android stacktrace (see debuggerd output).

=================================================================
    Managed Stacktrace:
=================================================================
      at <unknown> <0xffffffff>
      at System.Threading._ThreadPoolWaitCallback:PerformWaitCallback <0x00007>
      at <Module>:runtime_invoke_bool <0x0006f>
=================================================================

06-04 12:57:31.509 E/mono-rt (29535): 707fd000-70903000 rw-p 00000000 fd:01 1032302                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.509 E/mono-rt (29535): 70903000-7094d000 rw-p 00000000 fd:01 1032304                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.509 E/mono-rt (29535): 7094d000-70986000 rw-p 00000000 fd:01 1032306                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 70986000-7098a000 rw-p 00000000 fd:01 1032309                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 7098a000-709cd000 rw-p 00000000 fd:01 1032310                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 709cd000-70a08000 rw-p 00000000 fd:01 1032312                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 70a08000-71266000 rw-p 00000000 fd:01 1032313                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 71266000-7132e000 rw-p 00000000 fd:01 1032314                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 7132e000-71337000 rw-p 00000000 fd:01 1032315                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 71337000-71340000 rw-p 00000000 fd:01 1032316                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 71340000-71364000 rw-p 00000000 fd:01 1032317                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 71364000-7138c000 rw-p 00000000 fd:01 1032318                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 7138c000-7138d000 rw-p 00000000 fd:01 1032319                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 7138d000-71390000 rw-p 00000000 fd:01 1032320                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 71390000-713a9000 rw-p 00000000 fd:01 1032321                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 713a9000-713aa000 rw-p 00000000 fd:01 1032322                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 713aa000-713ab000 rw-p 00000000 fd:01 1032323                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 713ab000-713ad000 rw-p 00000000 fd:01 1032324                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 713ad000-713b3000 rw-p 00000000 fd:01 1032325                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 713b3000-713b4000 rw-p 00000000 fd:01 1032326                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 713b4000-713be000 rw-p 00000000 fd:01 1032327                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 E/mono-rt (29535): 713be000-71599000 r--p 00000000 fd:00 4226                               /system/framework/arm64/boot.oat
06-04 12:57:31.510 E/mono-rt (29535): 71599000-71c1a000 r-xp 001db000 fd:00 4226                               /system/framework/arm64/boot.oat
06-04 12:57:31.514 F/libc    (29535): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 29581 (Thread Pool Wor)

Output from adb:

06-04 12:57:31.415  1028  1043 I GBMv2   : GBM state [1]
06-04 12:57:31.509 29535 29581 E mono-rt : /proc/self/maps:
06-04 12:57:31.509 29535 29581 E mono-rt : 12c00000-52c00000 rw-p 00000000 00:01 22869                              /dev/ashmem/dalvik-main space (region space) (deleted)
06-04 12:57:31.509 29535 29581 E mono-rt : 70555000-707fd000 rw-p 00000000 fd:01 1032299                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.509 29535 29581 E mono-rt : 707fd000-70903000 rw-p 00000000 fd:01 1032302                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.509 29535 29581 E mono-rt : 70903000-7094d000 rw-p 00000000 fd:01 1032304                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.509 29535 29581 E mono-rt : 7094d000-70986000 rw-p 00000000 fd:01 1032306                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 70986000-7098a000 rw-p 00000000 fd:01 1032309                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 7098a000-709cd000 rw-p 00000000 fd:01 1032310                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 709cd000-70a08000 rw-p 00000000 fd:01 1032312                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 70a08000-71266000 rw-p 00000000 fd:01 1032313                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 71266000-7132e000 rw-p 00000000 fd:01 1032314                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 7132e000-71337000 rw-p 00000000 fd:01 1032315                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 71337000-71340000 rw-p 00000000 fd:01 1032316                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 71340000-71364000 rw-p 00000000 fd:01 1032317                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 71364000-7138c000 rw-p 00000000 fd:01 1032318                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 7138c000-7138d000 rw-p 00000000 fd:01 1032319                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 7138d000-71390000 rw-p 00000000 fd:01 1032320                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 71390000-713a9000 rw-p 00000000 fd:01 1032321                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 713a9000-713aa000 rw-p 00000000 fd:01 1032322                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 713aa000-713ab000 rw-p 00000000 fd:01 1032323                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 713ab000-713ad000 rw-p 00000000 fd:01 1032324                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 713ad000-713b3000 rw-p 00000000 fd:01 1032325                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 713b3000-713b4000 rw-p 00000000 fd:01 1032326                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 713b4000-713be000 rw-p 00000000 fd:01 1032327                            /data/dalvik-cache/arm64/system@[email protected]
06-04 12:57:31.510 29535 29581 E mono-rt : 713be000-71599000 r--p 00000000 fd:00 4226                               /system/framework/arm64/boot.oat
06-04 12:57:31.510 29535 29581 E mono-rt : 71599000-71c1a000 r-xp 001db000 fd:00 4226                               /system/framework/arm64/boot.oat
06-04 12:57:31.514 29535 29581 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 29581 (Thread Pool Wor)
06-04 12:57:31.573  1439  1552 I AutomaticBrightnessControllerEx: [MultiALC] lux = 179.0, time = 1030395609
06-04 12:57:31.624 29652 29652 I crash_dump64: obtaining output fd from tombstoned
06-04 12:57:31.625  1190  1190 I /system/bin/tombstoned: received crash request for pid 29535
06-04 12:57:31.630 29652 29652 I crash_dump64: performing dump of process 29535 (target tid = 29581)
06-04 12:57:31.631 29652 29652 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-04 12:57:31.631 29652 29652 F DEBUG   : Build fingerprint: 'lge/elsa_global_ca/elsa:8.0.0/OPR1.170623.032/181980931e4c8:user/release-keys'
06-04 12:57:31.631 29652 29652 F DEBUG   : Revision: '12'
06-04 12:57:31.631 29652 29652 F DEBUG   : ABI: 'arm64'
06-04 12:57:31.631 29652 29652 F DEBUG   : pid: 29535, tid: 29581, name: Thread Pool Wor  >>> hci.tractus.manager <<<
06-04 12:57:31.631 29652 29652 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20
06-04 12:57:31.631 29652 29652 F DEBUG   : Cause: null pointer dereference
06-04 12:57:31.631 29652 29652 F DEBUG   :     x0   0000000000000000  x1   00000074044b39a0  x2   0000000000000020  x3   0000000000000070
06-04 12:57:31.631 29652 29652 F DEBUG   :     x4   0000000000000000  x5   0000000000000000  x6   0000007403ffa0c8  x7   000000740df68000
06-04 12:57:31.631 29652 29652 F DEBUG   :     x8   0000000000000000  x9   0000000000000000  x10  0000000000000001  x11  0000007403ffafb0
06-04 12:57:31.631 29652 29652 F DEBUG   :     x12  0000000000000000  x13  00000073fdc04720  x14  00000000ffffffff  x15  0000000000048440
06-04 12:57:31.631 29652 29652 F DEBUG   :     x16  000000740df661f8  x17  000000740dd8d670  x18  00000074032944dc  x19  000000740df7d560
06-04 12:57:31.631 29652 29652 F DEBUG   :     x20  0000000000000002  x21  0000000000000000  x22  0000000000000000  x23  0000000000000074
06-04 12:57:31.631 29652 29652 F DEBUG   :     x24  0000000000000000  x25  0000000000000000  x26  0000007403ffb3b0  x27  00000073fdc078b8
06-04 12:57:31.631 29652 29652 F DEBUG   :     x28  00000074044b3000  x29  0000007403ffa6d0  x30  000000740dcd4658
06-04 12:57:31.631 29652 29652 F DEBUG   :     sp   0000007403ffa6d0  pc   000000740dd8d678  pstate 0000000000000000
06-04 12:57:31.632 29652 29652 F DEBUG   :
06-04 12:57:31.632 29652 29652 F DEBUG   : backtrace:
06-04 12:57:31.632 29652 29652 F DEBUG   :     #00 pc 0000000000177678  /data/app/Mono.Android.DebugRuntime-qeaK3X99NmwzDF-HSYR8BA==/lib/arm64/libmonosgen-64bit-2.0.so (mono_jit_info_get_method+8)
06-04 12:57:31.632 29652 29652 F DEBUG   :     #01 pc 00000000000be654  /data/app/Mono.Android.DebugRuntime-qeaK3X99NmwzDF-HSYR8BA==/lib/arm64/libmonosgen-64bit-2.0.so

eliaspuurunen on 4 Jun 2019

Can confirm, redmi note 5 - same issue when migrate runs in ef core

kkarakk on 5 Jun 2019

Reopening for now to use the closed status of this item to indicate when the fix is published.

brendanzagaeski on 5 Jun 2019

👍2

I am still running into this error on a HTTP request timeout in a seperate thread.
This happens using MobileServiceClient.LoginAsync("custom", loginData);


=================================================================
    Native Crash Reporting
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================06-06 09:35:51.495 E/mono-rt (20768): /proc/self/maps:

06-06 09:35:51.496 E/mono-rt (20768): 12c00000-52c00000 rw-p 00000000 00:01 18881                              /dev/ashmem/dalvik-main space (region space) (deleted)
06-06 09:35:51.496 E/mono-rt (20768): 6ff5a000-70202000 rw-p 00000000 103:08 905                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.496 E/mono-rt (20768): 70202000-70308000 rw-p 00000000 103:08 912                               /data/dalvik-cache/arm64/system@[email protected]
=================================================================
    Basic Fault Adddress Reporting
=================================================================
Memory around native instruction pointer (0x796978f678):0x796978f668  00 1c 40 b9 c0 03 5f d6 fd 7b bf a9 fd 03 00 91  ..@..._..{......
0x796978f678  08 20 40 b9 a8 00 c8 37 88 01 e0 37 00 00 40 f9  . @....7...7..@.
0x796978f688  fd 7b c1 a8 c0 03 5f d6 60 08 00 b0 01 0a 00 f0  .{...._.`.......
0x796978f698  03 0a 00 f0 00 24 06 91 21 80 08 91 63 8c 0a 91  .....$..!...c...

No native Android stacktrace (see debuggerd output).

=================================================================
    Managed Stacktrace:
=================================================================
      at <unknown> <0xffffffff>
      at System.Threading._ThreadPoolWaitCallback:PerformWaitCallback <0x00007>
      at <Module>:runtime_invoke_bool <0x0006f>
=================================================================

06-06 09:35:51.496 E/mono-rt (20768): 70308000-70352000 rw-p 00000000 103:08 923                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.496 E/mono-rt (20768): 70352000-70388000 rw-p 00000000 103:08 934                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.496 E/mono-rt (20768): 70388000-7038c000 rw-p 00000000 103:08 940                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.496 E/mono-rt (20768): 7038c000-703cf000 rw-p 00000000 103:08 942                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.496 E/mono-rt (20768): 703cf000-7040a000 rw-p 00000000 103:08 962                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.496 E/mono-rt (20768): 7040a000-70bf7000 rw-p 00000000 103:08 964                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.496 E/mono-rt (20768): 70bf7000-70c83000 rw-p 00000000 103:08 970                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.496 E/mono-rt (20768): 70c83000-70c8c000 rw-p 00000000 103:08 973                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70c8c000-70c95000 rw-p 00000000 103:08 975                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70c95000-70cb9000 rw-p 00000000 103:08 977                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70cb9000-70ce1000 rw-p 00000000 103:08 978                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70ce1000-70ce2000 rw-p 00000000 103:08 979                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70ce2000-70ce5000 rw-p 00000000 103:08 980                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70ce5000-70d70000 rw-p 00000000 103:08 981                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70d70000-70d97000 rw-p 00000000 103:08 982                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70d97000-70dd0000 rw-p 00000000 103:08 984                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70dd0000-70dd2000 rw-p 00000000 103:08 986                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70dd2000-70dd3000 rw-p 00000000 103:08 988                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70dd3000-70dd9000 rw-p 00000000 103:08 989                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70dd9000-70ddf000 rw-p 00000000 103:08 991                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70ddf000-70de4000 rw-p 00000000 103:08 993                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.497 E/mono-rt (20768): 70de4000-70deb000 rw-p 00000000 103:08 995                               /data/dalvik-cache/arm64/system@[email protected]
06-06 09:35:51.509 F/libc    (20768): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 20841 (Thread Pool Wor)

ThePizzaguy on 6 Jun 2019

The crash is NOT fixed in 16.1.2.

            try { throw new FileLoadException (); }
            catch (System.Exception e) when (e is FileLoadException) { }

06-06 10:41:11.877  7145  7145 E mono-rt : /proc/self/maps:
06-06 10:41:11.877  7145  7145 E mono-rt : 12c00000-17240000 rw-p 00000000 00:05 1004                               /dev/ashmem/dalvik-main space (region space) (deleted)
06-06 10:41:11.878  7145  7145 E mono-rt : 17240000-17800000 rw-p 04640000 00:05 1004                               /dev/ashmem/dalvik-main space (region space) (deleted)
06-06 10:41:11.878  7145  7145 E mono-rt : 17800000-17ac0000 ---p 04c00000 00:05 1004                               /dev/ashmem/dalvik-main space (region space) (deleted)
06-06 10:41:11.878  7145  7145 E mono-rt : 17ac0000-52c00000 rw-p 04ec0000 00:05 1004                               /dev/ashmem/dalvik-main space (region space) (deleted)
06-06 10:41:11.878  7145  7145 E mono-rt : 6f6fa000-6f9e8000 rw-p 00000000 103:2d 173314                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6f9e8000-6f9fe000 r--p 002ee000 103:2d 173314                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6f9fe000-6fb4a000 rw-p 00000000 103:2d 53188                             /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6fb4a000-6fb5c000 r--p 0014c000 103:2d 53188                             /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6fb5c000-6fb9f000 rw-p 00000000 103:2d 96190                             /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6fb9f000-6fba2000 r--p 00043000 103:2d 96190                             /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6fba2000-6fbe0000 rw-p 00000000 103:2d 108328                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6fbe0000-6fbe3000 r--p 0003e000 103:2d 108328                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6fbe3000-6fc69000 rw-p 00000000 103:2d 183038                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6fc69000-6fc70000 r--p 00086000 103:2d 183038                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6fc70000-6fcda000 rw-p 00000000 103:2d 183206                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6fcda000-6fce1000 r--p 0006a000 103:2d 183206                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6fce1000-6fd25000 rw-p 00000000 103:2d 227501                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6fd25000-6fd30000 r--p 00044000 103:2d 227501                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 6fd30000-70857000 rw-p 00000000 103:2d 227767                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 70857000-708bd000 r--p 00b27000 103:2d 227767                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 708bd000-70a19000 rw-p 00000000 103:2d 293104                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 70a19000-70a2b000 r--p 0015c000 103:2d 293104                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 70a2b000-70a3a000 rw-p 00000000 103:2d 293133                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 70a3a000-70a3c000 r--p 0000f000 103:2d 293133                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.878  7145  7145 E mono-rt : 70a3c000-70a58000 rw-p 00000000 103:2d 293141                            /data/dalvik-cache/arm64/system@[email protected]
06-06 10:41:11.880  7145  7145 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20 in tid 7145 (.dfd_posdb.app2), pid 7145 (.dfd_posdb.app2)


06-06 10:41:12.068  7537  7537 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
06-06 10:41:12.069   742   742 I /system/bin/tombstoned: received crash request for pid 7145
06-06 10:41:12.070  7537  7537 I crash_dump64: performing dump of process 7145 (target tid = 7145)
06-06 10:41:12.107  7537  7537 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-06 10:41:12.108  7537  7537 F DEBUG   : Build fingerprint: 'HUAWEI/BLA-L29/HWBLA:9/HUAWEIBLA-L29S/246C432R1:user/release-keys'
06-06 10:41:12.108  7537  7537 F DEBUG   : Revision: '0'
06-06 10:41:12.108  7537  7537 F DEBUG   : ABI: 'arm64'
06-06 10:41:12.108  7537  7537 F DEBUG   : pid: 7145, tid: 7145, name: .dfd_posdb.app2  >>> de.digitalkraft.dfd_posdb.app2 <<<
06-06 10:41:12.108  7537  7537 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x20
06-06 10:41:12.108  7537  7537 F DEBUG   : Cause: null pointer dereference
06-06 10:41:12.108  7537  7537 F DEBUG   :     x0  0000000000000000  x1  0000000000000000  x2  0000000000000000  x3  0000007ff5ad3c60
06-06 10:41:12.108  7537  7537 F DEBUG   :     x4  00000071f84d19a0  x5  0000007ff5ad3cf0  x6  0000000000000000  x7  0000000000000000
06-06 10:41:12.108  7537  7537 F DEBUG   :     x8  0000000000000000  x9  0000000000000000  x10 0000000000000000  x11 0000000000000000
06-06 10:41:12.108  7537  7537 F DEBUG   :     x12 0000000000000000  x13 0000000000000000  x14 00000071e5fe0000  x15 0000007ff5ad2c3c
06-06 10:41:12.108  7537  7537 F DEBUG   :     x16 00000071e5fde1f8  x17 00000071e5e05670  x18 00000071e5513a7c  x19 00000071e5ff5560
06-06 10:41:12.108  7537  7537 F DEBUG   :     x20 0000000000000002  x21 0000000000000000  x22 0000000000000000  x23 000000000000007f
06-06 10:41:12.108  7537  7537 F DEBUG   :     x24 0000000000000000  x25 0000000000000000  x26 0000007ff5ad3de0  x27 00000071e5513bc8
06-06 10:41:12.108  7537  7537 F DEBUG   :     x28 00000071f84d1000  x29 0000007ff5ad3100
06-06 10:41:12.108  7537  7537 F DEBUG   :     sp  0000007ff5ad3100  lr  00000071e5d4c658  pc  00000071e5e05678
06-06 10:41:12.109  7537  7537 F DEBUG   : 
06-06 10:41:12.109  7537  7537 F DEBUG   : backtrace:
06-06 10:41:12.109  7537  7537 F DEBUG   :     #00 pc 0000000000177678  /data/app/de.digitalkraft.dfd_posdb.app2-ufw-aLvuYDXt2P3NLXpmxg==/lib/arm64/libmonosgen-2.0.so (mono_jit_info_get_method+8)
06-06 10:41:12.215  1934  2083 I chatty  : uid=1000(system) HwWifiStatStore expire 17 lines

tobiasschulz on 6 Jun 2019

Reopening for now to use the closed status of this item to indicate when the fix is published.

brendanzagaeski on 6 Jun 2019

Noticed this recently when I had a null pointer. It never showed a null pointer error and showed this error instead.

neville-nazerane on 7 Jun 2019

Candidate development installer packages that include the fix:

Xamarin.Android.Sdk.9.3.0.23.vsix for Windows
xamarin.android-9.3.0-23.pkg for macOS (for users on the Preview channel of Visual Studio for Mac)

Installing and uninstalling these experimental packages

brendanzagaeski on 11 Jun 2019

👍10 🎉2

Note that by chance of timing, this new candidate Xamarin.Android SDK version won't be included quite yet in the next upcoming Visual Studio 2019 version 16.1.3 release. I will update this issue again when the fix has been published as part of Visual Studio 2019.

brendanzagaeski on 11 Jun 2019

The visx package is working for us.
We've successfully tested with three devices that weren't working previously.
Thanks!

darkblackcorner on 11 Jun 2019

👍2

Reopening for now to use the closed status of this item to indicate when the fix is published.

brendanzagaeski on 11 Jun 2019

👍3

Xamarin.Android WebClient app crash without an internet connection is fixed with Xamarin.Android.Sdk.9.3.0.23.vsix Thanks for fix

PiTi2k5 on 13 Jun 2019

👍1

crash when clearing entry binded to numeric solved (https://github.com/xamarin/Xamarin.Forms/issues/6336) . thanks

ish-1313 on 14 Jun 2019

👍2

I started experiencing this after the latest update, but in my case it was NOT resolved by installing the VSIX above. However, this only happens on release builds, and the problem dissapears when changing from D8/R8 to Proguard, but the (unmodified) code worked perfectly with R8/D8 before the update.

herreruud on 16 Jun 2019

👍1

@herreruud, thanks for the information! That sounds like it is probably a separate problem. If you get a chance, if you could file new issue with some details like the full text of the error message you are seeing, any zipped up example project or steps to reproduce you can share, and the adb logcat logs, that would be perfect. Thanks in advance!

brendanzagaeski on 18 Jun 2019

Can confirm that the provided vsix resolved the issue. Still not nice to wake up and see hundreds of crashes on Play Store...

Drutol on 20 Jun 2019

Had a sigsegv 11 error when doing Database.Migrate() using sqlite3 (EF etc.) and can confirm - this VSIX finally fixed the issue

Please proceed with making it into official xamarin

Minorsonek on 20 Jun 2019

https://github.com/xamarin/xamarin-android/issues/3222#issuecomment-505354685

acaliaro on 25 Jun 2019

Windows fix published. The new Xamarin.Android SDK version 9.3.0.23 that includes the fix for this issue has now been published as part of Visual Studio 2019 version 16.1.4. Check for the latest updates or install the most recent release from https://visualstudio.microsoft.com/downloads/ to get the fix.

macOS fix published. The new Xamarin.Android SDK version 9.3.0.23 that includes the fix for this issue has now been released in the Stable updater channel in Visual Studio for Mac. Check for the latest updates or install the most recent release from https://visualstudio.microsoft.com/downloads/ to get the fix.

Thanks again for submitting this report that helped bring the fix to Visual Studio!

brendanzagaeski on 25 Jun 2019

🎉7 ❤4

Installed, recompiled, debugged. Seems to work fine! Thanks @brendanzagaeski and others!

acaliaro on 26 Jun 2019

👍1

Ok, I can confirm that updating VS to 16.1.4 fixed the issue for me. Thanks!

NickeManarin on 26 Jun 2019

👍1

my case also fixed. thank you again

ish-1313 on 26 Jun 2019

👍1

This is not fixed for me. I'm using Visual Studio 16.1.4, with the latest NuGet packages.

=================================================================

Native Crash Reporting

Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries

used by your application.

=================================================================

Basic Fault Adddress Reporting

Memory around native instruction pointer (0xbe151068):0xbe151058 00 00 00 00 40 40 1f be 14 01 00 00 0c 00 00 00 ....@@..........
0xbe151068 88 e2 48 c8 0a 00 00 00 00 1d 1f ee 70 82 07 be ..H.........p...
0xbe151078 30 b2 14 be 00 00 00 00 00 01 00 00 00 00 00 00 0...............
0xbe151088 00 00 00 00 00 80 59 cc 0c 80 59 cc 18 80 59 cc ......Y...Y...Y.

No native Android stacktrace (see debuggerd output).

=========================================================06-30 14:17:27.711 E/mono-rt ( 4853): /proc/self/maps:

========

Managed Stacktrace:

  at <unknown> <0xffffffff>
  at clo@588-171:Invoke <0x00077>
  at Microsoft.FSharp.Control.AsyncPrimitives:CallThenInvokeNoHijackCheck <0x000d7>
  at Bind@495-1:Invoke <0x000b3>
  at Enceladus-Mobile-Common-IUserStore-GetUserFromCacheAsync@142-2:Invoke <0x00083>
  at Bind@495-1:Invoke <0x000b3>
  at clo@86-34:Invoke <0x00083>
  at Microsoft.FSharp.Control.AsyncPrimitives:CallThenInvoke <0x0029b>
  at Delay@1095:Invoke <0x0015f>
  at clo@85-36:Invoke <0x000eb>
  at Bind@495-1:Invoke <0x000b3>
  at Microsoft.FSharp.Control.Trampoline:Execute <0x0023f>
  at Microsoft.FSharp.Control.TrampolineHolder:ExecuteWithTrampoline <0x001cf>
  at Microsoft.FSharp.Control.AsyncPrimitives:continuation@973 <0x00107>
  at taskContinueWith@987:Invoke <0x000b3>
  at System.Threading.Tasks.ContinuationTaskFromResultTask`1:InnerInvoke <0x00143>
  at System.Threading.Tasks.Task:Execute <0x0007b>
  at System.Threading.Ta06-30 14:17:27.712 E/mono-rt ( 4853): 12c00000-12e00000 rw-p 00000000 00:05 30047                              /dev/ashmem/dalvik-main space (region space) (deleted)

sks.Task:ExecutionContextCallback <0x000af>
at System.Threading.ExecutionContext:RunInternal <0x0040b>
at System.Threading.ExecutionContext:Run <0x00073>
at System.Threading.Tasks.Task:ExecuteWithThreadLocal <0x00227>
at System.Threading.Tasks.Task:ExecuteEntry <0x001d7>
at System.Threading.Tasks.Task:System.Threading.IThreadPoolWorkItem.ExecuteWorkItem <0x0005f>
at System.Threading.ThreadPoolWorkQueue:Dispatch <0x00507>
at System.Threading._ThreadPoolWaitCallback:PerformWaitCallback <0x0007f>
at :runtime_invoke_bool <0x0007b>
=================================================================06-30 14:17:27.712 E/mono-rt ( 4853): 12e00000-12f80000 ---p 00200000 00:05 30047 /dev/ashmem/dalvik-main space (region space) (deleted)

06-30 14:17:27.712 E/mono-rt ( 4853): 12f80000-12fc0000 rw-p 00380000 00:05 30047 06-30 14:17:27.712 E/mono-rt ( 4853): 12fc0000-13040000 ---p 003c0000 00:05 30047 06-30 14:17:27.712 E/mono-rt ( 4853): 13040000-13080000 rw-p 00440000 00:05 30047 06-30 14:17:27.712 E/mono-rt ( 4853): 13080000-13140000 ---p 00480000 00:05 30047 06-30 14:17:27.712 E/mono-rt ( 4853): 13140000-2ac00000 rw-p 00540000 00:05 30047 06-30 14:17:27.712 E/mono-rt ( 4853): 6f44d000-6f468000 rw-p 00000000 103:24 1147231 06-30 14:17:27.712 E/mono-rt ( 4853): 6f468000-6f46b000 r--p 0001b000 103:24 1147231 06-30 14:17:27.712 E/mono-rt ( 4853): 6f46b000-6f46d000 rw-p 00000000 103:24 1147247 06-30 14:17:27.712 E/mono-rt ( 4853): 6f46d000-6f46e000 r--p 00002000 103:24 1147247 06-30 14:17:27.712 E/mono-rt ( 4853): 6f46e000-6f46f000 rw-p 00000000 103:24 1147250 06-30 14:17:27.712 E/mono-rt ( 4853): 6f46f000-6f470000 r--p 00001000 103:24 1147250 06-30 14:17:27.712 E/mono-rt ( 4853): 6f470000-6f471000 rw-p 00000000 103:24 1147253 06-30 14:17:27.712 E/mono-rt ( 4853): 6f471000-6f473000 rw-p 00000000 103:24 1147256 06-30 14:17:27.712 E/mono-rt ( 4853): 6f473000-6f474000 r--p 00002000 103:24 1147256 06-30 14:17:27.712 E/mono-rt ( 4853): 6f474000-6f689000 rw-p 00000000 103:24 1147259 06-30 14:17:27.712 E/mono-rt ( 4853): 6f689000-6f69d000 r--p 00215000 103:24 1147259 06-30 14:17:27.712 E/mono-rt ( 4853): 6f69d000-6f794000 rw-p 00000000 103:24 1147262 06-30 14:17:27.712 E/mono-rt ( 4853): 6f794000-6f7a6000 r--p 000f7000 103:24 1147262 06-30 14:17:27.712 E/mono-rt ( 4853): 6f7a6000-6f7d7000 rw-p 00000000 103:24 1147265 06-30 14:17:27.712 E/mono-rt ( 4853): 6f7d7000-6f7da000 r--p 00031000 103:24 1147265 06-30 14:17:27.712 E/mono-rt ( 4853): 6f7da000-6f807000 rw-p 00000000 103:24 1147268 06-30 14:17:27.712 E/mono-rt ( 4853): 6f807000-6f80a000 r--p 0002d000 103:24 1147268 06-30 14:17:27.712 E/mono-rt ( 4853): 6f80a000-6f860000 rw-p 00000000 103:24 1147271 06-30 14:17:27.714 F/libc ( 4853): Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), /dev/ashmem/dalvik-main space (region space) (deleted)
/dev/ashmem/dalvik-main space (region space) (deleted)
/dev/ashmem/dalvik-main space (region space) (deleted)
/dev/ashmem/dalvik-main space (region space) (deleted)
/dev/ashmem/dalvik-main space (region space) (deleted)
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
/data/dalvik-cache/arm/system@[email protected]
fault addr 0xbe151068 in tid 4962 (Thread Pool Wor), pid 4853

SpiegelSoft on 30 Jun 2019

@SpiegelSoft, thanks for the additional information! That crash would be something different from this issue (#3112) since the stack trace is from an arm ABI application rather than an arm64 ABI application. Based on the "code 2 (SEGV_ACCERR)" signal code you're seeing, I suspect you might be encountering the issue reported in https://github.com/xamarin/xamarin-android/issues/3198.

If you might have a project you can zip up and share on https://github.com/xamarin/xamarin-android/issues/3198 that demonstrates this problem, that would be excellent. See the latest comment there for a few possible options to share the project publicly or privately. Thanks in advance!

brendanzagaeski on 30 Jun 2019

It´s happening again today after 16.7.1 update...

jvillaro on 12 Aug 2020

@jvillaro, most likely you are seeing https://github.com/xamarin/xamarin-android/issues/4983. See https://github.com/xamarin/xamarin-android/issues/4983#issuecomment-670603943 for a way to workaround that issue. If that does not resolve the issue you are seeing, then please submit a new issue. Thanks in advance!

brendanzagaeski on 12 Aug 2020

Hi! Yes, it worked perfectly. Thanks!

On Wed, Aug 12, 2020 at 12:08 PM Brendan Zagaeski notifications@github.com
wrote:

@jvillaro https://github.com/jvillaro, most likely you are seeing #4983
https://github.com/xamarin/xamarin-android/issues/4983. See #4983
(comment)
https://github.com/xamarin/xamarin-android/issues/4983#issuecomment-670603943
for a way to workaround that issue. If that does not resolve the issue you
are seeing, then please submit a new issue. Thanks in advance!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/xamarin/xamarin-android/issues/3112#issuecomment-672931056,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJUZCJX5EW4PNWXQUOAUTGTSAKV5ZANCNFSM4HOU6YCQ
.

--
Saludos,
José A. Villaró M.

jvillaro on 12 Aug 2020

@jvillaro, most likely you are seeing #4983. See #4983 (comment) for a way to workaround that issue. If that does not resolve the issue you are seeing, then please submit a new issue. Thanks in advance!

Spent a day one this .... But thank you. Finally able to hit my breakpoints.
Application was working just fine in release mode though.