Xamarin-android: App crashes with debugger attached
Steps to Reproduce
- Debug app
- App crashes randomly
Expected Behavior
App runs without random crashes
Actual Behavior
When the App crashes it outputs a crash report, without having any useful stack trace to the App being at fault.
=================================================================
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 (0x7414eaa494):0x7414eaa484 60 0b 00 35 88 66 40 f9 08 01 00 b4 0a 01 40 79 `..5.f@.......@y
0x7414eaa494 a9 be 80 b9 5f 01 09 6b 8b 00 00 54 08 0d 09 8b ...._..k...T....
0x7414eaa4a4 16 05 40 f9 d6 0a 00 b5 7f 02 00 b9 e6 67 ff 97 [email protected]..
0x7414eaa4b4 e0 03 15 aa 2e 59 fe 97 96 66 40 f9 f6 01 00 b4 .....Y...f@.....
No native Android stacktrace (see debuggerd output).
===============================================04-03 13:07:12.816 E/mono-rt (28243): /proc/self/maps:
==================
Managed Stacktrace:
=================================================================
domain required for stack walk=================================================================
04-03 13:07:12.817 E/mono-rt (28243): 12c00000-12cc0000 rw-p 00000000 00:05 13719 /dev/ashmem/dalvik-main space (region space) (deleted)
04-03 13:07:12.817 E/mono-rt (28243): 12cc0000-12f80000 ---p 000c0000 00:05 13719 /dev/ashmem/dalvik-main space (region space) (deleted)
04-03 13:07:12.817 E/mono-rt (28243): 12f80000-13940000 rw-p 00380000 00:05 13719 /dev/ashmem/dalvik-main space (region space) (deleted)
04-03 13:07:12.817 E/mono-rt (28243): 13940000-1d980000 ---p 00d40000 00:05 13719 /dev/ashmem/dalvik-main space (region space) (deleted)
04-03 13:07:12.817 E/mono-rt (28243): 1d980000-1db80000 rw-p 0ad80000 00:05 13719 /dev/ashmem/dalvik-main space (region space) (deleted)
04-03 13:07:12.817 E/mono-rt (28243): 1db80000-1dc80000 rw-p 0af80000 00:05 13719 /dev/ashmem/dalvik-main space (region space) (deleted)
04-03 13:07:12.817 E/mono-rt (28243): 1dc80000-52c00000 rw-p 0b080000 00:05 13719 /dev/ashmem/dalvik-main space (region space) (deleted)
04-03 13:07:12.817 E/mono-rt (28243): 70158000-70170000 rw-p 00000000 103:01 1310729 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 70170000-70172000 r--p 00018000 103:01 1310729 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 70172000-70173000 rw-p 00000000 103:01 1310735 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 70173000-70174000 r--p 00001000 103:01 1310735 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 70174000-70176000 rw-p 00000000 103:01 1310741 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 70176000-70177000 r--p 00002000 103:01 1310741 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 70177000-70178000 rw-p 00000000 103:01 1310747 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 70178000-70179000 r--p 00001000 103:01 1310747 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 70179000-7043d000 rw-p 00000000 103:01 1310753 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 7043d000-70451000 r--p 002c4000 103:01 1310753 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 70451000-70586000 rw-p 00000000 103:01 1310759 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 70586000-70598000 r--p 00135000 103:01 1310759 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 70598000-705d7000 rw-p 00000000 103:01 1310765 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 705d7000-705da000 r--p 0003f000 103:01 1310765 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 705da000-70616000 rw-p 00000000 103:01 1310771 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 70616000-70619000 r--p 0003c000 103:01 1310771 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 70619000-7067f000 rw-p 00000000 103:01 1310777 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.817 E/mono-rt (28243): 7067f000-70686000 r--p 00066000 103:01 1310777 /data/dalvik-cache/arm64/system@[email protected]
04-03 13:07:12.818 F/libc (28243): Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xbc in tid 28304 (pool-4-thread-1), pid 28243 (.TrackMan.Range)
When trying to debug with VS for Mac I only get:
[mono-rt] /proc/self/maps:
[mono-rt] 12c00000-13680000 rw-p 00000000 00:05 31230 /dev/ashmem/dalvik-main space (region space)_5189_5189 (deleted)
[mono-rt] 13680000-137c0000 ---p 00a80000 00:05 31230 /dev/ashmem/dalvik-main space (region space)_5189_5189 (deleted)
[mono-rt] 137c0000-15440000 rw-p 00bc0000 00:05 31230 /dev/ashmem/dalvik-main space (region space)_5189_5189 (deleted)
[mono-rt] 15440000-15740000 ---p 02840000 00:05 31230 /dev/ashmem/dalvik-main space (region space)_5189_5189 (deleted)
[mono-rt] 15740000-52c00000 rw-p 02b40000 00:05 31230 /dev/ashmem/dalvik-main space (region space)_5189_5189 (deleted)
[mono-rt] 6f126000-6f400000 rw-p 00000000 103:0f 16 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f400000-6f416000 r--p 002da000 103:0f 16 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f416000-6f54b000 rw-p 00000000 103:0f 28 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f54b000-6f55d000 r--p 00135000 103:0f 28 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f55d000-6f59d000 rw-p 00000000 103:0f 34 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f59d000-6f5a0000 r--p 00040000 103:0f 34 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f5a0000-6f5e7000 rw-p 00000000 103:0f 43 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f5e7000-6f5eb000 r--p 00047000 103:0f 43 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f5eb000-6f651000 rw-p 00000000 103:0f 50 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f651000-6f658000 r--p 00066000 103:0f 50 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f658000-6f6b9000 rw-p 00000000 103:0f 53 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f6b9000-6f6c0000 r--p 00061000 103:0f 53 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f6c0000-6f704000 rw-p 00000000 103:0f 56 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f704000-6f70f000 r--p 00044000 103:0f 56 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 6f70f000-70326000 rw-p 00000000 103:0f 62 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 70326000-70386000 r--p 00c17000 103:0f 62 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 70386000-70510000 rw-p 00000000 103:0f 80 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 70510000-7052e000 r--p 0018a000 103:0f 80 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 7052e000-7053d000 rw-p 00000000 103:0f 86 /data/dalvik-cache/arm64/system@[email protected]
[mono-rt] 7053d000-7053f000 r--p 0000f000 103:0f 86 /data/dalvik-cache/arm64/system@[email protected]
[libc] Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xbc in tid 27358 (AsyncTask #5), pid 27108 (.TrackMan.Range)
Version Information
Latest version of VS for Mac stable or VS2019 GA (was also an issue on VS2019 Preview 4.4)
=== Visual Studio Enterprise 2019 for Mac ===
Version 8.0 (build 3001)
Installation UUID: e39f69fe-f899-4e46-a9a8-17ff8f869cb3
GTK+ 2.24.23 (Raleigh theme)
Xamarin.Mac 5.6.0.2 (d16-0 / 040682909)
Package version: 518010003
=== Mono Framework MDK ===
Runtime:
Mono 5.18.1.3 (2018-08/fdb26b0a445) (64-bit)
Package version: 518010003
=== NuGet ===
Version: 4.8.2.5835
=== .NET Core ===
Runtime: /usr/local/share/dotnet/dotnet
Runtime Versions:
2.1.9
2.1.8
2.1.7
2.1.6
2.1.5
SDK: /usr/local/share/dotnet/sdk/2.1.505/Sdks
SDK Versions:
2.1.505
2.1.504
2.1.503
2.1.500
2.1.403
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin/Sdks
=== Xamarin.Profiler ===
Version: 1.6.9
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler
=== Updater ===
Version: 11
=== Xamarin.Android ===
Version: 9.2.0.5 (Visual Studio Enterprise)
Android SDK: /Users/tci/Library/Android/sdk
Supported Android versions:
6.0 (API level 23)
7.0 (API level 24)
7.1 (API level 25)
8.1 (API level 27)
SDK Tools Version: 26.1.1
SDK Platform Tools Version: 28.0.1
SDK Build Tools Version: 28.0.3
Build Information:
Mono: mono/mono/2018-08-rc@5ad371dab1b
Java.Interop: xamarin/java.interop/d16-0@c987483
LibZipSharp: grendello/LibZipSharp/master@44de300
LibZip: nih-at/libzip/rel-1-5-1@b95cf3f
MXE: xamarin/mxe/xamarin@b9cbb535
ProGuard: xamarin/proguard/master@905836d
SQLite: xamarin/sqlite/3.26.0@325e91a
Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-0@0a7edd6
=== Microsoft Mobile OpenJDK ===
Java SDK: /Users/tci/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_8.0.25
1.8.0-25
Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL
=== Android Device Manager ===
Version: 1.2.0.14
Hash: 86df26f
Branch: remotes/origin/d16-0
Build date: 2019-03-27 18:41:02 UTC
=== Apple Developer Tools ===
Xcode 10.1 (14460.46)
Build 10B61
=== Xamarin.Mac ===
Version: 5.6.0.25 (Visual Studio Enterprise)
Hash: 50f75273
Branch: d16-0
Build date: 2019-03-05 11:50:33-0800
=== Xamarin.iOS ===
Version: 12.6.0.25 (Visual Studio Enterprise)
Hash: 50f75273
Branch: d16-0
Build date: 2019-03-05 11:50:33-0800
=== Xamarin Designer ===
Version: 4.17.4.414
Hash: 55b8d07ef
Branch: remotes/origin/d16-0
Build date: 2019-03-22 21:44:12 UTC
=== Xamarin Inspector ===
Version: 1.4.3
Hash: db27525
Branch: 1.4-release
Build date: Mon, 09 Jul 2018 21:20:18 GMT
Client compatibility: 1
=== Build Information ===
Release ID: 800003001
Git revision: 16b11d379aeff65cd1e81d3616c267ad4251ad36
Build date: 2019-03-28 13:14:24+00
Build branch: master
Xamarin extensions: efad41c7f410d8e6d43361236e0e778cf6f9b4a5
=== Operating System ===
Mac OS X 10.13.6
Darwin 17.7.0 Darwin Kernel Version 17.7.0
Thu Dec 20 21:47:19 PST 2018
root:xnu-4570.71.22~1/RELEASE_X86_64 x86_64
Additional Information
I got some help from @grendello to debug the issue and tried the following:
- Adding an environment.txt file to the App to increase what is being logged. That yielded the following log:
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=AppWindowToken{e06d450 token=Token{7deda13 ActivityRecord{b4e2102 u0 dk.TrackMan.Range/dk.TrackMan.SplashScreen t148}}})/@0x492bab0 - animation-leash)/@0xb2b8e08, nativeObject=515906067584, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=5a5d6a7 NavigationBar)/@0xe459edc - animation-leash)/@0xb93ad11, nativeObject=515907470240, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=512dde7 StatusBar)/@0xf8d1253 - animation-leash)/@0x7a88d03, nativeObject=516060250112, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=5a5d6a7 NavigationBar)/@0xe459edc - animation-leash)/@0x4904975, nativeObject=515934594048, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=e81e8ee SnapshotStartingWindow for taskId=148)/@0x94a536f - animation-leash)/@0xbccf4dc, nativeObject=515934593664, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Warning (5741) / System: A resource failed to call release.
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=AppWindowToken{e98764e token=Token{595ed49 ActivityRecord{9314750 u0 dk.TrackMan.Range/md552e608b944995f090b52594b40e05f58.RootView t148}}})/@0xb09a95a - animation-leash)/@0xde62136, nativeObject=515934883392, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=AppWindowToken{df4009d token=Token{1c10374 ActivityRecord{29d7f47 u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView t148}}})/@0x8a6c410 - animation-leash)/@0x6b5401a, nativeObject=515907473120, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=Dim Layer for - Task=148)/@0x8b8872f - animation-leash)/@0x29bcec5, nativeObject=515887426112, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=fbb672b dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0xf074b07 - animation-leash)/@0x4b057d2, nativeObject=515934883104, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=Dim Layer for - Task=148)/@0x84390a3 - animation-leash)/@0x9ba7759, nativeObject=515882971328, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=fbb672b dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0xf074b07 - animation-leash)/@0x23303f7, nativeObject=516060254240, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=Dim Layer for - Task=148)/@0x84390a3 - animation-leash)/@0xb794ccd, nativeObject=516060254720, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=95ae8c9 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x33596da - animation-leash)/@0xf21e801, nativeObject=515934885216, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=Dim Layer for - Task=148)/@0x7e646a6 - animation-leash)/@0x8daec94, nativeObject=515888486016, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=95ae8c9 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x33596da - animation-leash)/@0xadd5cf5, nativeObject=515887430048, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=Dim Layer for - Task=148)/@0x7e646a6 - animation-leash)/@0xf9c98fb, nativeObject=516582275232, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=98b865c dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0xe78ac48 - animation-leash)/@0x2d6c7, nativeObject=515888485632, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=Dim Layer for - Task=148)/@0x39044f4 - animation-leash)/@0xdeb2692, nativeObject=515882981600, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=98b865c dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0xe78ac48 - animation-leash)/@0x16b3e8c, nativeObject=515888492448, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=Dim Layer for - Task=148)/@0x39044f4 - animation-leash)/@0x910f5ea, nativeObject=515882982176, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=512dde7 StatusBar)/@0xf8d1253 - animation-leash)/@0x23e053, nativeObject=515888480544, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=5a5d6a7 NavigationBar)/@0xe459edc - animation-leash)/@0x1a5b68e, nativeObject=515882975168, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=512dde7 StatusBar)/@0xf8d1253 - animation-leash)/@0x45a3f9, nativeObject=515230059392, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=5a5d6a7 NavigationBar)/@0xe459edc - animation-leash)/@0xd40f2ec, nativeObject=516060256160, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=fa99816 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x79f1fa2 - animation-leash)/@0x7da7d69, nativeObject=515887425344, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=Dim Layer for - Task=148)/@0x27393ee - animation-leash)/@0x4dcef1c, nativeObject=515882982944, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=AppWindowToken{df4009d token=Token{1c10374 ActivityRecord{29d7f47 u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView t148}}})/@0x8a6c410 - animation-leash)/@0xd2e8395, nativeObject=515888491968, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=AppWindowToken{e98764e token=Token{595ed49 ActivityRecord{9314750 u0 dk.TrackMan.Range/md552e608b944995f090b52594b40e05f58.RootView t148}}})/@0xb09a95a - animation-leash)/@0xa1843e4, nativeObject=515888487840, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=Dim Layer for - Task=148)/@0x27393ee - animation-leash)/@0xeef1702, nativeObject=515883772192, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=AppWindowToken{e98764e token=Token{595ed49 ActivityRecord{9314750 u0 dk.TrackMan.Range/md552e608b944995f090b52594b40e05f58.RootView t148}}})/@0xb09a95a - animation-leash)/@0x6a97075, nativeObject=516060257984, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=AppWindowToken{4c9d381 token=Token{b788368 ActivityRecord{9cbf68b u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView t148}}})/@0xeab8444 - animation-leash)/@0x755deae, nativeObject=516060257504, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Debug (5741) / SurfaceControl: finalize(protected), animation-leash is released by finalize, sc=Surface(name=Surface(name=Dim Layer for - Task=148)/@0x9e9bf3 - animation-leash)/@0x4803b29, nativeObject=515934888768, caller=java.lang.Daemons$FinalizerDaemon.doFinalize:250 java.lang.Daemons$FinalizerDaemon.runInternal:237 java.lang.Daemons$Daemon.run:103 java.lang.Thread.run:764 <bottom of call stack> <bottom of call stack> <bottom of call stack>
Info (5741) / AfterimageCompensationService: BRIGHTNESS = 76
Debug (5741) : mAFPC_Read - w = 1080, h = 2280, s = 8, f = 4, s_size = 9922560, luminance = 76, count = 82, captureOrientation = 0
Verbose (5227) / APM_AudioPolicyManager: AudioPolicyManager:setRecordSilenced(uid:10024, silenced:1)
Debug (5741) / CustomFrequencyManagerService: FrequencyrequestList.getNextSchedTuneBoostRequest, index: 0
Debug (5741) / InputReader: Input event(7): value=1 when=84994.634821
Debug (5741) / InputReader: Input event(7): value=1 when=84994.634821
Info (5741) / InputReader: Touch event's action is 0x0 (deviceType=0) [pCnt=1, s=0.375 ] when=84994.634821
Info (5741) / clp-JNI: Add pinfo. (channel) 29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView (server) (pkg) AppWindowToken{4c9d381 token=Token{b788368 ActivityRecord{9cbf68b u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView t148}}} 31484 10243 (action) 0
Info (5741) / clp-JNI: Add pinfo end.
Info (5741) / InputDispatcher: Delivering touch to (31484): action: 0x0, displayId: 0, '29a8674', toolType: 1
Info (5741) / Pageboost: Launcher App Execution
Info (5741) / Pageboost: vramdisk hit dk.TrackMan.Range
Debug (31484) / ViewRootImpl@c6e57c[ActivityFlowHostView]: ViewPostIme pointer 0
Debug (5741) / WifiTrafficPoller: TrafficStats TxPkts=119237 RxPkts=279553 TxBytes=17971770 RxBytes=362284066 , Foreground uid=10243 pkgName=dk.TrackMan.Range TxPackets=7141 RxPackets=8949 TxBytes=657173 RxBytes=7544180
Debug (5741) / WifiPermissionsUtil: canAccessScanResults: pkgName = android, uid = 1000
Debug (5741) / InputReader: Input event(7): value=0 when=84994.726355
Debug (5741) / InputReader: Input event(7): value=0 when=84994.726355
Info (5741) / InputReader: Touch event's action is 0x1 (deviceType=0) [pCnt=1, s=] when=84994.726355
Info (5741) / clp-JNI: Add pinfo. (channel) 29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView (server) (pkg) AppWindowToken{4c9d381 token=Token{b788368 ActivityRecord{9cbf68b u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView t148}}} 31484 10243 (action) 1
Info (5741) / clp-JNI: Add pinfo end.
Info (5741) / InputDispatcher: Delivering touch to (31484): action: 0x1, displayId: 0, '29a8674', toolType: 1
Debug (31484) / ViewRootImpl@c6e57c[ActivityFlowHostView]: ViewPostIme pointer 1
Debug (5741) / WifiPermissionsUtil: canAccessScanResults: pkgName = com.sec.android.sdhms, uid = 1000
Error (5231) / BufferQueueProducer: [dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView[31484]#1] disconnect: not connected (req=1)
Warning (31484) / libEGL: EGLNativeWindowType 0x780764b010 disconnect failed
Debug (31484) / OpenGLRenderer: eglDestroySurface = 0x780ac15780, 0x780764b000
Debug (31484) / ViewRootImpl@c6e57c[ActivityFlowHostView]: dispatchDetachedFromWindow
Debug (31484) / ViewRootImpl@c6e57c[ActivityFlowHostView]: Surface release. android.view.ViewRootImpl.doDie:7944 android.view.ViewRootImpl.die:7912 android.view.WindowManagerGlobal.removeViewLocked:497 android.view.WindowManagerGlobal.removeView:435 android.view.WindowManagerImpl.removeViewImmediate:124 android.app.Dialog.dismissDialog:518 android.app.Dialog.dismiss:501 mono.android.view.View_OnClickListenerImplementor.n_onClick:-2
Verbose (5741) / WindowManager: Remove Window{29a8674 u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView}: mSurfaceController=Surface(name=dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView[31484])/@0xfa667e3 mAnimatingExit=false mRemoveOnExit=false mHasSurface=true surfaceShowing=true isAnimationSet=false app-animation=false mWillReplaceWindow=false inPendingTransaction=false mDisplayFrozen=false callers=com.android.server.wm.WindowState.removeIfPossible:2710 com.android.server.wm.WindowManagerService.removeWindow:1921 com.android.server.wm.Session.remove:253 android.view.IWindowSession$Stub.onTransact:261 com.android.server.wm.Session.onTransact:186 android.os.Binder.execTransact:739
Info (5741) / WindowManager: Cancelling animation restarting=true, leash=null, surface=Surface(name=29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x5cd4f5e, parent=Surface(name=AppWindowToken{4c9d381 token=Token{b788368 ActivityRecord{9cbf68b u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView t148}}})/@0xeab8444, caller=com.android.server.wm.SurfaceAnimator.startAnimation:119 com.android.server.wm.WindowContainer.startAnimation:1213 com.android.server.wm.WindowState.startAnimation:5783 com.android.server.wm.WindowState.startAnimation:5766 com.android.server.wm.WindowStateAnimator.applyAnimationLocked:1785
Info (5741) / WindowManager: Reparenting to leash, surface=Surface(name=29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x5cd4f5e, caller=com.android.server.wm.SurfaceAnimator.startAnimation:127 com.android.server.wm.WindowContainer.startAnimation:1213 com.android.server.wm.WindowState.startAnimation:5783 com.android.server.wm.WindowState.startAnimation:5766 com.android.server.wm.WindowStateAnimator.applyAnimationLocked:1785
Info (5231) / SurfaceFlinger: id=982 createSurf (6080x6080),2 flag=4, Surface(name=29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x5cd4f5e - animation-leash#0
Debug (5741) / SurfaceControl: reparent is called, sc=Surface(name=29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x5cd4f5e, newParentHandle=android.os.BinderProxy@fa83710, transaction=android.view.SurfaceControl$Transaction@c4c300c, caller=com.android.server.wm.SurfaceAnimator.createAnimationLeash:387 com.android.server.wm.SurfaceAnimator.startAnimation:127 com.android.server.wm.WindowContainer.startAnimation:1213 com.android.server.wm.WindowState.startAnimation:5783 com.android.server.wm.WindowState.startAnimation:5766 com.android.server.wm.WindowStateAnimator.applyAnimationLocked:1785 com.android.server.wm.WindowState.removeIfPossible:2804
Verbose (5741) / WindowManager: Changing focus from Window{29a8674 u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView EXITING} to Window{7066e14 u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView} Callers=com.android.server.wm.WindowState.setupWindowForRemoveOnExit:2860 com.android.server.wm.WindowState.removeIfPossible:2831 com.android.server.wm.WindowState.removeIfPossible:2710 com.android.server.wm.WindowManagerService.removeWindow:1921
Debug (5741) / StatusBarManagerService: notifyRequestedSystemKey recent=false home=false
Info (5741) / WindowManager: Cancelling animation restarting=true, leash=null, surface=Surface(name=Dim Layer for - Task=148)/@0x39b036a, parent=Surface(name=Task=148)/@0xb7b4d29, caller=com.android.server.wm.SurfaceAnimator.startAnimation:119 com.android.server.wm.-$$Lambda$yACUZqn1Ak-GL14-Nu3kHUSaLX0.startAnimation:0 com.android.server.wm.Dimmer.startAnim:406 com.android.server.wm.Dimmer.startDimExit:393 com.android.server.wm.Dimmer.updateDims:350
Info (5741) / WindowManager: Reparenting to leash, surface=Surface(name=Dim Layer for - Task=148)/@0x39b036a, caller=com.android.server.wm.SurfaceAnimator.startAnimation:127 com.android.server.wm.-$$Lambda$yACUZqn1Ak-GL14-Nu3kHUSaLX0.startAnimation:0 com.android.server.wm.Dimmer.startAnim:406 com.android.server.wm.Dimmer.startDimExit:393 com.android.server.wm.Dimmer.updateDims:350
Info (5231) / SurfaceFlinger: id=983 createSurf (6080x6080),2 flag=4, Surface(name=Dim Layer for - Task=148)/@0x39b036a - animation-leash#0
Debug (5741) / SurfaceControl: reparent is called, sc=Surface(name=Dim Layer for - Task=148)/@0x39b036a, newParentHandle=android.os.BinderProxy@91a4c0e, transaction=android.view.SurfaceControl$Transaction@762117d, caller=com.android.server.wm.SurfaceAnimator.createAnimationLeash:387 com.android.server.wm.SurfaceAnimator.startAnimation:127 com.android.server.wm.-$$Lambda$yACUZqn1Ak-GL14-Nu3kHUSaLX0.startAnimation:0 com.android.server.wm.Dimmer.startAnim:406 com.android.server.wm.Dimmer.startDimExit:393 com.android.server.wm.Dimmer.updateDims:350 com.android.server.wm.Task.prepareSurfaces:902
Debug (5231) / Layer: [29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView#0]::reparent oldParent:[AppWindowToken{4c9d381 token=Token{b788368 ActivityRecord{9cbf68b u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView t148}}}#0], newParent:[Surface(name=29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x5cd4f5e - animation-leash#0]
Debug (5741) / InputDispatcher: Focus left window (31484): 29a8674 0
Debug (5741) / InputDispatcher: Focus entered window (31484): 7066e14 0
Debug (5741) / InputTransport: Input channel destroyed: fd=471
Debug (5741) / WindowManager: reportFocusChangedSerialized, focused=true, inTouchMode=true, win=Window{7066e14 u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView}
Debug (5741) / WindowManager: reportFocusChangedSerialized, focused=false, inTouchMode=true, win=Window{29a8674 u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView EXITING}
Debug (31484) / InputTransport: Input channel destroyed: fd=95
Debug (31484) / ViewRootImpl@793d1f0[ActivityFlowHostView]: MSG_WINDOW_FOCUS_CHANGED 1 1
Debug (5741) / WindowManager: setSystemUiVisibility: vis= 0x9016, fullscreenVis= 0x0, dockedVis= 0x0, win=Window{7066e14 u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView}
Debug (5231) / Layer: [Dim Layer for - Task=148#0]::reparent oldParent:[Task=148#0], newParent:[Surface(name=Dim Layer for - Task=148)/@0x39b036a - animation-leash#0]
Debug (17759) / LightBarController: onNavigationVisibilityChanged : vis = 9016, nbModeChanged = false navigationBarMode = 4
Debug (5741) / SamsungPhoneWindowManager: adjustSystemUiVisibilityLw: vis=0x9016
Debug (5741) / InputManager-JNI: setSystemUiVisibility dexmode: false changed: true displayid: 0 visibility: 0x9016 DD: 0x9016 OD: 0x0
Debug (31484) / InputMethodManager: prepareNavigationBarInfo() DecorView@8e09b84[ActivityFlowHostView]
Debug (31484) / InputMethodManager: getNavigationBarColor() -855310
Debug (31484) / InputMethodManager: prepareNavigationBarInfo() DecorView@8e09b84[ActivityFlowHostView]
Debug (31484) / InputMethodManager: getNavigationBarColor() -855310
Verbose (31484) / InputMethodManager: Starting input: tba=dk.TrackMan.Range ic=null mNaviBarColor -855310 mIsGetNaviBarColorSuccess true , NavVisible : false , NavTrans : false
Debug (31484) / InputMethodManager: startInputInner - Id : 0
Info (31484) / InputMethodManager: startInputInner - mService.startInputOrWindowGainedFocus
Debug (5741) / InputMethodManagerService: startInputOrWindowGainedFocus : windowGainedFocus
Debug (5741) / InputMethodManagerService: windowGainedFocus: destinationUserId (getCallingUid) = 0
Debug (5741) / InputMethodManagerService: windowGainedFocus: currentUserId=0
Debug (5741) / InputMethodManagerService: windowGainedFocus: mCurrentFocusedUserId=0
Debug (5741) / InputMethodManagerService: windowGainedFocus : lock - currentUserId = 0 destinationUserId = 0
Debug (5741) / InputMethodManagerService: windowGainedFocus : mCurrentFocusedUserId - 0 and mSecureKeypadEnabled - false, userSwitched - false
Verbose (5741) / InputMethodManagerService: windowGainedFocus : reason=WINDOW_FOCUS_GAIN client=android.os.BinderProxy@26c94f7 inputContext=null missingMethods= attribute=android.view.inputmethod.EditorInfo@e41b43c nm = dk.TrackMan.Range controlFlags=#101 softInputMode=#12 windowFlags=#81810100
Debug (5741) / InputMethodManagerService: checkDisplayOfStartInputAndUpdateKeyboard display Id 0last 0
Debug (5741) / InputMethodManagerService: setCurrentInputInfo - inputContext : null eidtorInfo : android.view.inputmethod.EditorInfo@e41b43c missingMethods : 0
Debug (5741) / InputTransport: Input channel constructed: fd=471
Debug (5741) / InputTransport: Input channel destroyed: fd=471
Debug (31484) / InputTransport: Input channel constructed: fd=95
Debug (31484) / InputTransport: Input channel destroyed: fd=116
Info (19520) / InputMethodWrapper: call dispatchStartInputWithToken
Info (19520) / InputMethodService: dispatchStartInputWithToken
Info (19520) / SKBD_Performance: [IIManager] [PF_CL][onFinishInput] 195615
Debug (19520) / InputMethodService: checkDisplayOfStartInputAndUpdateKeyboard display Id 0last 0
Error (31484) / ViewRootImpl: sendUserActionEvent() returned.
Info (19520) / SKBD: SamsungKeypad [IMI] onStartInput - caller pid : 31484, caller uid : 10243
Info (5741) / WindowManager: reset, Reparenting to original parent, shouldDeferScheduleAnimation=false, destroyLeash=true, surface=Surface(name=Dim Layer for - Task=148)/@0x39b036a, parent=Surface(name=Task=148)/@0xb7b4d29, parentNativeHandle=android.os.BinderProxy@49495c2, caller=com.android.server.wm.SurfaceAnimator.lambda$getFinishedCallback$0:94 com.android.server.wm.-$$Lambda$SurfaceAnimator$SIBia0mND666K8lMCPsoid8pUTI.run:4 com.android.server.wm.SurfaceAnimator.lambda$getFinishedCallback$1:101 com.android.server.wm.-$$Lambda$SurfaceAnimator$vdRZk66hQVbQCvVXEaQCT1kVmFc.onAnimationFinished:4 com.android.server.wm.LocalAnimationAdapter.lambda$startAnimation$0:65
Debug (5741) / SurfaceControl: reparent is called, sc=Surface(name=Dim Layer for - Task=148)/@0x39b036a, newParentHandle=android.os.BinderProxy@49495c2, transaction=android.view.SurfaceControl$Transaction@762117d, caller=com.android.server.wm.SurfaceAnimator.reset:328 com.android.server.wm.SurfaceAnimator.lambda$getFinishedCallback$0:94 com.android.server.wm.-$$Lambda$SurfaceAnimator$SIBia0mND666K8lMCPsoid8pUTI.run:4 com.android.server.wm.SurfaceAnimator.lambda$getFinishedCallback$1:101 com.android.server.wm.-$$Lambda$SurfaceAnimator$vdRZk66hQVbQCvVXEaQCT1kVmFc.onAnimationFinished:4 com.android.server.wm.LocalAnimationAdapter.lambda$startAnimation$0:65 com.android.server.wm.-$$Lambda$LocalAnimationAdapter$X--EomqUvw4qy89IeeTFTH7aCMo.run:4
Debug (5741) / SurfaceControl: destroy(transaction), animation-leash is destroyed, sc=Surface(name=Surface(name=Dim Layer for - Task=148)/@0x39b036a - animation-leash)/@0x432d62f, transaction=android.view.SurfaceControl$Transaction@762117d, caller=com.android.server.wm.SurfaceAnimator.reset:335 com.android.server.wm.SurfaceAnimator.lambda$getFinishedCallback$0:94 com.android.server.wm.-$$Lambda$SurfaceAnimator$SIBia0mND666K8lMCPsoid8pUTI.run:4 com.android.server.wm.SurfaceAnimator.lambda$getFinishedCallback$1:101 com.android.server.wm.-$$Lambda$SurfaceAnimator$vdRZk66hQVbQCvVXEaQCT1kVmFc.onAnimationFinished:4 com.android.server.wm.LocalAnimationAdapter.lambda$startAnimation$0:65 com.android.server.wm.-$$Lambda$LocalAnimationAdapter$X--EomqUvw4qy89IeeTFTH7aCMo.run:4
Info (5231) / SurfaceFlinger: id=980 Removed Dim Layer for - Task=148#0 (0/73)
Info (5741) / WindowManager: reset, Reparenting to original parent, shouldDeferScheduleAnimation=false, destroyLeash=true, surface=Surface(name=29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x5cd4f5e, parent=Surface(name=AppWindowToken{4c9d381 token=Token{b788368 ActivityRecord{9cbf68b u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView t148}}})/@0xeab8444, parentNativeHandle=android.os.BinderProxy@f2674a4, caller=com.android.server.wm.SurfaceAnimator.lambda$getFinishedCallback$0:94 com.android.server.wm.-$$Lambda$SurfaceAnimator$SIBia0mND666K8lMCPsoid8pUTI.run:4 com.android.server.wm.SurfaceAnimator.lambda$getFinishedCallback$1:101 com.android.server.wm.-$$Lambda$SurfaceAnimator$vdRZk66hQVbQCvVXEaQCT1kVmFc.onAnimationFinished:4 com.android.server.wm.LocalAnimationAdapter.lambda$startAnimation$0:65
Debug (5741) / SurfaceControl: reparent is called, sc=Surface(name=29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x5cd4f5e, newParentHandle=android.os.BinderProxy@f2674a4, transaction=android.view.SurfaceControl$Transaction@c4c300c, caller=com.android.server.wm.SurfaceAnimator.reset:328 com.android.server.wm.SurfaceAnimator.lambda$getFinishedCallback$0:94 com.android.server.wm.-$$Lambda$SurfaceAnimator$SIBia0mND666K8lMCPsoid8pUTI.run:4 com.android.server.wm.SurfaceAnimator.lambda$getFinishedCallback$1:101 com.android.server.wm.-$$Lambda$SurfaceAnimator$vdRZk66hQVbQCvVXEaQCT1kVmFc.onAnimationFinished:4 com.android.server.wm.LocalAnimationAdapter.lambda$startAnimation$0:65 com.android.server.wm.-$$Lambda$LocalAnimationAdapter$X--EomqUvw4qy89IeeTFTH7aCMo.run:4
Debug (5741) / SurfaceControl: destroy(transaction), animation-leash is destroyed, sc=Surface(name=Surface(name=29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x5cd4f5e - animation-leash)/@0x1c68209, transaction=android.view.SurfaceControl$Transaction@c4c300c, caller=com.android.server.wm.SurfaceAnimator.reset:335 com.android.server.wm.SurfaceAnimator.lambda$getFinishedCallback$0:94 com.android.server.wm.-$$Lambda$SurfaceAnimator$SIBia0mND666K8lMCPsoid8pUTI.run:4 com.android.server.wm.SurfaceAnimator.lambda$getFinishedCallback$1:101 com.android.server.wm.-$$Lambda$SurfaceAnimator$vdRZk66hQVbQCvVXEaQCT1kVmFc.onAnimationFinished:4 com.android.server.wm.LocalAnimationAdapter.lambda$startAnimation$0:65 com.android.server.wm.-$$Lambda$LocalAnimationAdapter$X--EomqUvw4qy89IeeTFTH7aCMo.run:4
Error (5741) / WindowManager: win=Window{29a8674 u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView EXITING} destroySurfaces: appStopped=false win.mWindowRemovalAllowed=true win.mRemoveOnExit=true win.mViewVisibility=0 caller=com.android.server.wm.AppWindowToken.destroySurfaces:870 com.android.server.wm.AppWindowToken.destroySurfaces:851 com.android.server.wm.WindowState.onExitAnimationDone:5366 com.android.server.wm.WindowStateAnimator.onAnimationFinished:319 com.android.server.wm.WindowState.onAnimationFinished:5788 com.android.server.wm.-$$Lambda$yVRF8YoeNdTa8GR1wDStVsHu8xM.run:2 com.android.server.wm.SurfaceAnimator.lambda$getFinishedCallback$0:97
Info (5741) / WindowManager: Destroying surface Surface(name=dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView[31484])/@0xfa667e3 called by com.android.server.wm.WindowStateAnimator.destroySurface:1880 com.android.server.wm.WindowStateAnimator.destroySurfaceLocked:838 com.android.server.wm.WindowState.destroySurfaceUnchecked:3775 com.android.server.wm.WindowState.destroySurface:3756 com.android.server.wm.AppWindowToken.destroySurfaces:870 com.android.server.wm.AppWindowToken.destroySurfaces:851 com.android.server.wm.WindowState.onExitAnimationDone:5366 com.android.server.wm.WindowStateAnimator.onAnimationFinished:319
Info (5231) / SurfaceFlinger: id=978 Removed dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView[31484]#1 (0/72)
Debug (5741) / WindowManager: clearSavedLeashOnCommit, savedLeash=Surface(name=Surface(name=29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x5cd4f5e - animation-leash)/@0x1c68209, caller=com.android.server.wm.WindowContainer.removeImmediately:337 com.android.server.wm.WindowState.removeImmediately:2622 com.android.server.wm.WindowState.destroySurface:3759 com.android.server.wm.AppWindowToken.destroySurfaces:870 com.android.server.wm.AppWindowToken.destroySurfaces:851 com.android.server.wm.WindowState.onExitAnimationDone:5366
Info (5741) / SensorService: [REARLIGHT] lux value : 102, code value : 109
Warning (5231) / SurfaceFlinger: Attempting to set client state on removed layer: dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView[31484]#1 [s.what : 64]
Debug (5231) / Layer: [29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView#0]::reparent oldParent:[Surface(name=29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x5cd4f5e - animation-leash#0], newParent:[AppWindowToken{4c9d381 token=Token{b788368 ActivityRecord{9cbf68b u0 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView t148}}}#0]
Warning (5231) / SurfaceFlinger: Attempting to set client state on removed layer: Dim Layer for - Task=148#0 [s.what : 65536]
Warning (5231) / SurfaceFlinger: Attempting to destroy on removed layer: dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView[31484]#1
Info (5231) / SurfaceFlinger: id=977 Removed 29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView#0 (2/71)
Warning (5231) / SurfaceFlinger: Attempting to destroy on removed layer: Dim Layer for - Task=148#0
Info (5231) / SurfaceFlinger: id=983 Removed Surface(name=Dim Layer for - Task=148)/@0x39b036a - animation-leash#0 (1/70)
Info (5231) / SurfaceFlinger: id=982 Removed Surface(name=29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x5cd4f5e - animation-leash#0 (2/69)
Info (5231) / Layer: id=977 onRemoved 29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView#0
Info (5231) / Layer: id=982 onRemoved Surface(name=29a8674 dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView)/@0x5cd4f5e - animation-leash#0
Info (5231) / Layer: id=980 onRemoved Dim Layer for - Task=148#0
Info (5231) / Layer: id=983 onRemoved Surface(name=Dim Layer for - Task=148)/@0x39b036a - animation-leash#0
Info (5231) / Layer: id=978 onRemoved dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView[31484]#1
Debug (5741) / WifiStateMachine: enter getWifiLinkLayerStats
Info (5741) / WifiVendorHal: getWifiLinkLayerStats(l.2965) before calling iface.getLinkLayerStats
Info (5212) / [email protected]: enter getLinkLayerStats
Info (5212) / [email protected]: enter getLinkLayerStatsInternal
Info (5231) / SurfaceFlinger: Display 0 HWC layers:
Info (5231) / SurfaceFlinger: type | handle | flag | format | source crop (l,t,r,b) | frame | name
Info (5231) / SurfaceFlinger: ------------+--------------+------+-----------+----------------------------+---------------------+------
Info (5231) / SurfaceFlinger: SolidColor | | 0004 | Unknown | 0.0 0.0 -1.0 -1.0 | 0 0 1080 112 | Letterbox - top#1
Info (5231) / SurfaceFlinger: Device | 0x7823642180 | 0002 | RGBA_8888 | 0.0 0.0 1080.0 2168.0 | 0 112 1080 2280 | dk.TrackMan.Range/md51bc303ec2e30c20[...]1a9e67.ActivityFlowHostView[31484]#0
Info (5231) / SurfaceFlinger: Device | 0x7823049460 | 0000 | RGBA_8888 | 0.0 0.0 67.0 431.0 | 1013 870 1080 1301 | com.samsung.android.app.cocktailbars[...]rservice.CocktailBarService[20894]#0
Info (5231) / SurfaceFlinger:
Info (5212) / [email protected]: Successfully getLinkLayerStats.
Info (5741) / WifiVendorHal: getWifiLinkLayerStats(l.2965) after calling iface.getLinkLayerStats
Info (5741) / WifiStateMachine: checkScoreBasedQuality - mPreviousScore[0]:72 mPreviousScore[1]:72 mPreviousScore[2]:73 s2Score:73mPrevoiusScoreAverage:72
Error (5741) / Watchdog: !@Sync 2828 [2019-04-03 15:38:44.501] FD count : 584
Info (5741) / SensorService: [REARLIGHT] lux value : 101, code value : 109
Verbose (5227) / APM_AudioPolicyManager: AudioPolicyManager:setRecordSilenced(uid:10041, silenced:1)
Debug (5741) / WifiPermissionsUtil: canAccessScanResults: pkgName = android, uid = 1000
Debug (17759) / SecStatusBarWifiView: updateState: WifiIconState(resId=2131232608, visible=true, activityId=2131232613)
Debug (5741) / CustomFrequencyManagerService: FrequencyrequestList.getNextSchedTuneBoostRequest, index: 0
Warning (31484) / .TrackMan.Rang: 0xebadde09 skipped times: 0
Error (31484) / mono-rt: /proc/self/maps:
Error (31484) / mono-rt: 12c00000-135c0000 rw-p 00000000 00:05 31230 /dev/ashmem/dalvik-main space (region space)_5189_5189 (deleted)
Error (31484) / mono-rt: 135c0000-13740000 ---p 009c0000 00:05 31230 /dev/ashmem/dalvik-main space (region space)_5189_5189 (deleted)
Error (31484) / mono-rt: 13740000-17b00000 rw-p 00b40000 00:05 31230 /dev/ashmem/dalvik-main space (region space)_5189_5189 (deleted)
Error (31484) / mono-rt: 17b00000-17b80000 ---p 04f00000 00:05 31230 /dev/ashmem/dalvik-main space (region space)_5189_5189 (deleted)
Error (31484) / mono-rt: 17b80000-52c00000 rw-p 04f80000 00:05 31230 /dev/ashmem/dalvik-main space (region space)_5189_5189 (deleted)
Error (31484) / mono-rt: 6f126000-6f400000 rw-p 00000000 103:0f 16 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f400000-6f416000 r--p 002da000 103:0f 16 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f416000-6f54b000 rw-p 00000000 103:0f 28 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f54b000-6f55d000 r--p 00135000 103:0f 28 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f55d000-6f59d000 rw-p 00000000 103:0f 34 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f59d000-6f5a0000 r--p 00040000 103:0f 34 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f5a0000-6f5e7000 rw-p 00000000 103:0f 43 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f5e7000-6f5eb000 r--p 00047000 103:0f 43 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f5eb000-6f651000 rw-p 00000000 103:0f 50 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f651000-6f658000 r--p 00066000 103:0f 50 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f658000-6f6b9000 rw-p 00000000 103:0f 53 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f6b9000-6f6c0000 r--p 00061000 103:0f 53 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f6c0000-6f704000 rw-p 00000000 103:0f 56 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f704000-6f70f000 r--p 00044000 103:0f 56 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 6f70f000-70326000 rw-p 00000000 103:0f 62 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 70326000-70386000 r--p 00c17000 103:0f 62 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 70386000-70510000 rw-p 00000000 103:0f 80 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 70510000-7052e000 r--p 0018a000 103:0f 80 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 7052e000-7053d000 rw-p 00000000 103:0f 86 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / mono-rt: 7053d000-7053f000 r--p 0000f000 103:0f 86 /data/dalvik-cache/arm64/system@[email protected]
Error (31484) / libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xbc in tid 31527 (AsyncTask #4), pid 31484 (.TrackMan.Range)
Info (31859) / crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
Info (5407) : received crash request for pid 31527
Info (31859) / crash_dump64: performing dump of process 31484 (target tid = 31527)
Error (31859) / DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Error (31859) / DEBUG: Build fingerprint: 'samsung/beyond1lteeea/beyond1:9/PPR1.180610.011/G973FXXU1ASCA:user/release-keys'
Error (31859) / DEBUG: Revision: '26'
Error (31859) / DEBUG: ABI: 'arm64'
Error (31859) / DEBUG: pid: 31484, tid: 31527, name: AsyncTask #4 >>> dk.TrackMan.Range <<<
Error (31859) / DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xbc
Error (31859) / DEBUG: Cause: null pointer dereference
Error (31859) / DEBUG: x0 0000000000000000 x1 000000783e57c648 x2 00000078264e7148 x3 0000000000000008
Error (31859) / DEBUG: x4 0000000000000000 x5 0000000000000002 x6 000000780f84c698 x7 0000000000000009
Error (31859) / DEBUG: x8 000000783e59e898 x9 0000000000000001 x10 0000000000000001 x11 0000007820000000
Error (31859) / DEBUG: x12 00000000000000a3 x13 0000007820000000 x14 000000000000000d x15 aaaaaaaaaaaaaaab
Error (31859) / DEBUG: x16 000000782e3589c0 x17 00000078cc6c794c x18 0000000000000000 x19 00000078264e7148
Error (31859) / DEBUG: x20 000000783e57c648 x21 0000000000000000 x22 00000078200a3e06 x23 0000007840506b40
Error (31859) / DEBUG: x24 0000000000000000 x25 0000007812997990 x26 0000000000000000 x27 000000000000000b
Error (31859) / DEBUG: x28 0000000000000000 x29 00000078264e7130
Error (31859) / DEBUG: sp 00000078264e70a0 lr 000000782e1af484 pc 000000782e1af494
Error (31859) / DEBUG:
Error (31859) / DEBUG: backtrace:
Error (31859) / DEBUG: #00 pc 0000000000199494 /data/app/Mono.Android.DebugRuntime-lFcdnuZ4gxhgNloh2F5UDw==/lib/arm64/libmonosgen-64bit-2.0.so
Debug (5741) / WifiConnectivityMonitor.DnsPingerHandler: setCurrentLinkProperties: lp={InterfaceName: wlan0 LinkAddresses: [fe80::aa15:4cdf:530c:59b1/64,192.168.17.3/24,] Routes: [fe80::/64 -> :: wlan0,192.168.17.0/24 -> 0.0.0.0 wlan0,0.0.0.0/0 -> 192.168.17.1 wlan0,] DnsAddresses: [83.136.89.6,83.136.89.4,] UsePrivateDns: false PrivateDnsServerName: null Domains: null MTU: 0 TcpBufferSizes: 524288,1048576,4194304,524288,1048576,4194304}
Debug (5741) / WifiPermissionsUtil: canAccessScanResults: pkgName = android, uid = 1000
Debug (5741) / WifiPermissionsUtil: canAccessScanResults: pkgName = android, uid = 1000
Debug (5741) / WifiConnectivityMonitor.DnsPingerHandler: #1 GW MAC address found in ARP table.0 msec.
Error (5407) : Tombstone written to: /data/tombstones/tombstone_02
Info (5741) / BootReceiver: Copying /data/tombstones/tombstone_02 to DropBox (SYSTEM_TOMBSTONE)
Warning (5741) / ActivityManager: crash : dk.TrackMan.Range,0
Error (5181) / audit: type=1701 audit(1554298726.009:1420): auid=4294967295 uid=10243 gid=10243 ses=4294967295 subj=u:r:untrusted_app_27:s0:c512,c768 pid=31484 comm=4173796E635461736B202334 exe="/system/bin/app_process64" sig=11 res=1
Warning (5741) / ActivityManager: Force finishing activity dk.TrackMan.Range/md51bc303ec2e30c20fab671d92b41a9e67.ActivityFlowHostView
@grendello then asked me to try run the App with lldb. However, I didn't get that to work, it just made my App hang on splash screen and left some props on the device that made the subsequent launches of the app fail. I followed the instructions here: https://github.com/mono/lldb-binaries had to mess with the xa-lldb script to make it pick up the correct Main Activity and make it use msbuild because xabuild is not present on my machine.
After the failed lldb attempt, @grendello asked me to run
msbuild /bl /t:_Gdbon the App project, which didn't seem to crash the App. Which lead @grendello to the conclusion: "that means it might be a problem with sdb or triggered by it". And here we are.
I cannot attach a repro sample, because I don't know which part of it actually triggers the App to blow up, since there is no stack trace to go from.
This issue seems to mainly happen on arm64 devices. My Nexus 5, doesn't have any issues with debugging.
Other people on Gitter.im had a similar issue.
Cheesebaron
All 60 comments
Another couple issues that look related:
JonDouglas
on 3 Apr 2019
Detailed repro steps here with full source: https://github.com/dotMorten/XamarinFormsControls/issues/41#issuecomment-479535534
dotMorten
on 3 Apr 2019
@lambdageek please handle this issue
marek-safar
on 3 Apr 2019
I can also reproduce this issue, on Win10 with VS2019.
Here's a sample repro :
https://github.com/crogeniks/XamarinCrash
Reproduced devices :
Getac ZX70 (intel processor, 64bit) Android 5.1
Getac Z710 ( arm processor, guessing 32bit ) Android 4.1
--------- beginning of crash
04-03 10:35:37.877 12557-12673/? A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x50 in tid 12673 (Thread-2664)
04-03 10:35:37.879 12557-12595/? D/ufoEGL: Pixel Format : GGL_PIXEL_FORMAT_RGBA_8888
04-03 10:35:37.983 2588-2588/? I/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
04-03 10:35:37.983 2588-2588/? I/DEBUG: Build fingerprint: 'Getac/zx70/zx70:5.1.1/LMY47Z/user.builder.20160531.095103:user/release-keys'
04-03 10:35:37.983 2588-2588/? I/DEBUG: Revision: '0'
04-03 10:35:37.983 2588-2588/? I/DEBUG: ABI: 'x86'
04-03 10:35:37.983 2588-2588/? I/DEBUG: pid: 12557, tid: 12673, name: Thread-2664 >>> com.isaac.scan <<<
04-03 10:35:37.983 2588-2588/? I/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x50
04-03 10:35:37.992 2588-2588/? I/DEBUG: eax f3f85ba8 ebx ef67e1f0 ecx 00000000 edx 00000001
04-03 10:35:37.992 2588-2588/? I/DEBUG: esi f3f760b8 edi d518db08
04-03 10:35:37.992 2588-2588/? I/DEBUG: xcs 00000023 xds 0000002b xes 0000002b xfs 00000000 xss 0000002b
04-03 10:35:37.992 2588-2588/? I/DEBUG: eip ef4ca3ff ebp 00000000 esp d518da80 flags 00210282
04-03 10:35:37.992 2588-2588/? I/DEBUG: backtrace:
04-03 10:35:37.992 2588-2588/? I/DEBUG: #00 pc 001d63ff /data/app/com.isaac.scan-1/lib/x86/libmonosgen-2.0.so
04-03 10:35:38.163 2588-2588/? W/libbacktrace: virtual bool Backtrace::VerifyReadWordArgs(uintptr_t, word_t*): invalid pointer 0xef5d7a8a
04-03 10:35:38.275 2588-2588/? I/DEBUG: Tombstone written to: /data/tombstones/tombstone_03
crogeniks
on 3 Apr 2019
PureWeen
on 3 Apr 2019
Seeing this issue, too in a Xamarin.Forms application:
=================================================================
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.
=================================================================
04-03 16:50:03.889 E/mono-rt ( 9107): /proc/self/maps:
04-03 16:50:03.889 E/mono-rt ( 9107): 12c00000-12e80000 rw-p 00000000 00:05 10847 /dev/ashmem/dalvik-main space (region space) (deleted)
04-03 16:50:03.889 E/mono-rt ( 9107): 12e80000-13080000 ---p 00280000 00:05 10847 /dev/ashmem/dalvik-main space (region space) (deleted)
04-03 16:50:03.889 E/mono-rt ( 9107): 13080000-52c00000 rw-p 00480000 00:05 10847 /dev/ashmem/dalvik-main space (region space) (deleted)
=================================================================
Basic Fault Adddress Reporting
=================================================================
Memory around native instruction pointer (0xcab9f3ff):0xcab9f3ef 00 00 8b 6c 24 70 8b 46 78 85 c0 74 16 0f b7 10 ...l$p.Fx..t....
0xcab9f3ff 8b 4d 50 39 ca 7c 0c 8b 7c 88 04 85 ff 0f 85 54 .MP9.|..|......T
0xcab9f40f 01 00 00 8b 44 24 78 c7 00 00 00 00 00 e8 6f 65 ....D$x.......oe
0xcab9f41f fd ff 89 2c 24 e8 e7 ab f8 ff 8b 76 78 85 f6 74 ...,$......vx..t
No native Android stacktrace (see debuggerd output).
=================================================================
Managed Stacktrace:
=================================================================
domain required for stack walk=================================================================04-03 16:50:03.889 E/mono-rt ( 9107): 56b1f000-56b24000 r-xp 00000000 fd:01 2189 /system/bin/app_process32
04-03 16:50:03.889 E/mono-rt ( 9107): 56b24000-56b25000 r--p 00004000 fd:01 2189 /system/bin/app_process32
04-03 16:50:03.889 E/mono-rt ( 9107): 56b25000-56b26000 rw-p 00000000 00:00 0
04-03 16:50:03.889 E/mono-rt ( 9107): 70785000-709aa000 rw-p 00000000 fc:00 106503 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.889 E/mono-rt ( 9107): 709aa000-709c0000 r--p 00225000 fc:00 106503 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.889 E/mono-rt ( 9107): 709c0000-70ab7000 rw-p 00000000 fc:00 106506 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.889 E/mono-rt ( 9107): 70ab7000-70ac9000 r--p 000f7000 fc:00 106506 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.889 E/mono-rt ( 9107): 70ac9000-70afa000 rw-p 00000000 fc:00 106509 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.889 E/mono-rt ( 9107): 70afa000-70afd000 r--p 00031000 fc:00 106509 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.889 E/mono-rt ( 9107): 70afd000-70b2a000 rw-p 00000000 fc:00 106512 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.889 E/mono-rt ( 9107): 70b2a000-70b2d000 r--p 0002d000 fc:00 106512 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.889 E/mono-rt ( 9107): 70b2d000-70b83000 rw-p 00000000 fc:00 106515 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.889 E/mono-rt ( 9107): 70b83000-70b8a000 r--p 00056000 fc:00 106515 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.890 E/mono-rt ( 9107): 70b8a000-70bdf000 rw-p 00000000 fc:00 106518 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.890 E/mono-rt ( 9107): 70bdf000-70be6000 r--p 00055000 fc:00 106518 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.890 E/mono-rt ( 9107): 70be6000-70c21000 rw-p 00000000 fc:00 106521 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.891 E/mono-rt ( 9107): 70c21000-70c2c000 r--p 0003b000 fc:00 106521 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.891 E/mono-rt ( 9107): 70c2c000-7142d000 rw-p 00000000 fc:00 106524 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.891 E/mono-rt ( 9107): 7142d000-7148d000 r--p 00801000 fc:00 106524 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.891 E/mono-rt ( 9107): 7148d000-7156f000 rw-p 00000000 fc:00 106527 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.891 E/mono-rt ( 9107): 7156f000-71581000 r--p 000e2000 fc:00 106527 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.891 E/mono-rt ( 9107): 71581000-7158c000 rw-p 00000000 fc:00 106530 /data/dalvik-cache/x86/system@[email protected]
04-03 16:50:03.892 F/libc ( 9107): Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x50 in tid 9154 (AsyncTask #2), pid 9107 (PaccApp.Android)
Please let me know if I can provide further details to assist with the debugging.
markuspalme
on 3 Apr 2019
@lambdageek here is how I was able to reproduce (hit me up on Slack if you need more info):
- Clone this repo and open
XamarinFormsControls.sln: https://github.com/dotMorten/XamarinFormsControls - Debug
SampleApp.Android.csproj - Click the first button,
Simple Auto-Completion - Type a few characters in
Enter a country, hit back arrow - Repeat on step 3
You might have to do the cycle one time or more.
Once the app crashes, you can just launch the app by tapping the app icon. The crash seems to go away when no debugger is attached at all--no changes in app settings required.
jonathanpeppers
on 3 Apr 2019
@jonathanpeppers I never had to go beyond step 3 (always crashes 2-3 seconds after the page has loaded)
dotMorten
on 3 Apr 2019
Ok yes, maybe you can just wait a few seconds on that second page -- I may have been tapping buttons in a state of panic.
jonathanpeppers
on 3 Apr 2019
I found that issue occurs after some relatively constant amount of time no matter what I do in the app. The crash occurs also when using Rider.
orestesgaolin
on 4 Apr 2019
Hi, I encountered the same issue. With a Xamarin android native app and Visual Studio 2019 for Mac.
I just have to launch the app with the debugger attached on a emulator or a device and wait. The app crash after few seconds.
No crash when the debugger is not attached
sl-maelledelay
on 4 Apr 2019
I encounter this issue when i downgrade the xamarin.android to 9.1.8 and/or remove my d8/r8 settings in the .csproj. This all happened after updating to Visual Studios 2019. iOS works fine, but Android is not working for me.
gmoney494
on 4 Apr 2019
I have the same problem here. However, when I created a new Xamarin.Forms application in VS2019, the debugger stays attached. Very strange why my existing application constantly de-attachted by the debugger.
marcelbeeker
on 4 Apr 2019
I'm using an environment.txt with
debug.mono.debug=1
MONO_XDEBUG=1
MONO_SDB_ENV_OPTIONS=loglevel=10
MONO_LOG_LEVEL=debug
MONO_GC_DEBUG=10
Seeing this sort of thing when the crash is happening using the repro from https://github.com/xamarin/xamarin-android/issues/2920#issuecomment-479582065
[Mono] ves_icall_System_Threading_Events_ResetEvent_internal: resetting Event handle 0x9f793020
[Mono] ves_icall_System_Threading_Events_ResetEvent_internal: obtained write lock on Event handle 0x9f793020
[Mono] mono_w32handle_unref_core: unref Event handle 0x9f793020, ref: 2 -> 1 destroy: false
[Mono] mono_w32handle_ref_core: ref Event handle 0x9f793020, ref: 1 -> 2
[Mono] mono_w32handle_test_capabilities: testing 0x3 against 0x8 (0)
[Mono] mono_w32handle_test_capabilities: testing 0x3 against 0x1 (1)
[Mono] mono_w32handle_test_capabilities: testing 0x3 against 0x4 (0)
[Mono] mono_w32handle_timedwait_signal_handle: waiting for 0x9f793020 (type Event)
[Mono] mono_w32handle_ref_core: ref Event handle 0x9f793020, ref: 2 -> 3
[mono] [0x899ff920] Thread terminated, obj=0xa4004760, tls=0x89b23000.
[mono-rt] Stacktrace:
~In terms of app behavior, I hacked the suggest box to never have any suggestions. At this point the app crashes for me about a 2 seconds after I switch to the "simple auto-completion" page without any interaction. So it does make sense that the event code would be involved. (As for debugger - best guess so far is that the soft debugger just affects some timing between threads.)~
~Going to scrutinize the mono 2018-08 event related changes...~
Update: my guess here was wrong. See https://github.com/xamarin/xamarin-android/issues/2920#issuecomment-480929875 for a clean stack trace of what's going wrong. It's the debugger agent trying to process a thread_stopped profiler event from a thread that is already detached.
lambdageek
on 5 Apr 2019
Serious bugs like these should be given topmost priority, not stay unfixed for 4 days without any indication of when to expect a fix 🙄
Happypig375
on 7 Apr 2019
I'm also facing this problem after updating to recent Visual Studio for Mac 2019. Our Xamarin.Android app compiles and runs but slightly crashes after passing our custom splash screen. This only started happening after updating to the recent release.
Exact Xamarin version used is detailed below as well as Application Output showing the crash details.
=== Visual Studio Enterprise 2019 for Mac ===
Version 8.0.1 (build 1)
Installation UUID: 43da0aa5-4126-4bf1-80d6-82e3154be7ce
GTK+ 2.24.23 (Raleigh theme)
Xamarin.Mac 5.6.0.2 (d16-0 / 040682909)
Package version: 518010003
=== Mono Framework MDK ===
Runtime:
Mono 5.18.1.3 (2018-08/fdb26b0a445) (64-bit)
Package version: 518010003
=== NuGet ===
Version: 4.8.2.5835
=== .NET Core ===
Runtime: /usr/local/share/dotnet/dotnet
Runtime Versions:
2.1.9
2.1.2
SDK: /usr/local/share/dotnet/sdk/2.1.505/Sdks
SDK Versions:
2.1.505
2.1.302
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin/Sdks
=== Xamarin.Profiler ===
Version: 1.6.9
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler
=== Updater ===
Version: 11
=== Apple Developer Tools ===
Xcode 10.1 (14460.46)
Build 10B61
=== Xamarin.Mac ===
Xamarin.Mac not installed. Can't find /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/Version.
=== Xamarin.iOS ===
Version: 12.6.0.25 (Visual Studio Enterprise)
Hash: 50f75273
Branch: d16-0
Build date: 2019-03-05 11:50:33-0800
=== Xamarin Designer ===
Version: 4.17.4.414
Hash: 55b8d07ef
Branch: remotes/origin/d16-0
Build date: 2019-03-22 21:44:12 UTC
=== Xamarin.Android ===
Version: 9.2.0.5 (Visual Studio Enterprise)
Android SDK: /Users/mzekrallah/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
4.4 (API level 19)
5.0 (API level 21)
5.1 (API level 22)
6.0 (API level 23)
7.0 (API level 24)
7.1 (API level 25)
8.0 (API level 26)
8.1 (API level 27)
SDK Tools Version: 26.1.1
SDK Platform Tools Version: 28.0.1
SDK Build Tools Version: 28.0.3
Build Information:
Mono: mono/mono/2018-08-rc@5ad371dab1b
Java.Interop: xamarin/java.interop/d16-0@c987483
LibZipSharp: grendello/LibZipSharp/master@44de300
LibZip: nih-at/libzip/rel-1-5-1@b95cf3f
MXE: xamarin/mxe/xamarin@b9cbb535
ProGuard: xamarin/proguard/master@905836d
SQLite: xamarin/sqlite/3.26.0@325e91a
Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-0@0a7edd6
=== Microsoft Mobile OpenJDK ===
Java SDK: /Users/mzekrallah/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25
1.8.0-25
Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL
=== Android Device Manager ===
Version: 1.2.0.14
Hash: 86df26f
Branch: remotes/origin/d16-0
Build date: 2019-03-27 18:41:02 UTC
=== Xamarin Inspector ===
Version: 1.4.3
Hash: db27525
Branch: 1.4-release
Build date: Mon, 09 Jul 2018 21:20:18 GMT
Client compatibility: 1
=== Build Information ===
Release ID: 800010001
Git revision: 1a426f4ef97c415b9f3cbff9e548c7db5aee09cb
Build date: 2019-04-03 18:08:51+00
Build branch: master
Xamarin extensions: 6b0f7a364694e71268aead3d501c3c35485865b1
=== Operating System ===
Mac OS X 10.14.3
Darwin 18.2.0 Darwin Kernel Version 18.2.0
Thu Dec 20 20:46:53 PST 2018
root:xnu-4903.241.1~1/RELEASE_X86_64 x86_64
——————————————————————————————————————————
System.Threading[0xdf37a420]: 4
Thread started: #2
Thread started: <Thread Pool> #3
Thread started: <Thread Pool> #4
Thread started: <Thread Pool> #5
Thread started: <Thread Pool> #6
[Choreographer] Skipped 45 frames! The application may be doing too much work on its main thread.
Thread started: #7
[Mono] DllImport searching in: '__Internal' ('(null)').
[Mono] Searching for 'java_interop_jnienv_new_byte_array'.
[Mono] Probing 'java_interop_jnienv_new_byte_array'.
[Mono] Found as 'java_interop_jnienv_new_byte_array'.
[Mono] DllImport searching in: '__Internal' ('(null)').
[Mono] Searching for 'java_interop_jnienv_set_byte_array_region'.
[Mono] Probing 'java_interop_jnienv_set_byte_array_region'.
[Mono] Found as 'java_interop_jnienv_set_byte_array_region'.
[Mono] DllImport searching in: '__Internal' ('(null)').
[Mono] Searching for 'java_interop_jnienv_get_byte_array_region'.
[Mono] Probing 'java_interop_jnienv_get_byte_array_region'.
[Mono] Found as 'java_interop_jnienv_get_byte_array_region'.
[Choreographer] Skipped 53 frames! The application may be doing too much work on its main thread.
[zygote] JNI RegisterNativeMethods: attempt to register 0 native methods for md53bc541500e5fea3fd3cb8cbbbf3b7d2a.AdvancedButton
[Mono] DllImport searching in: '__Internal' ('(null)').
[Mono] Searching for 'java_interop_jnienv_new_int_array'.
[Mono] Probing 'java_interop_jnienv_new_int_array'.
[Mono] Found as 'java_interop_jnienv_new_int_array'.
[Mono] DllImport searching in: '__Internal' ('(null)').
[Mono] Searching for 'java_interop_jnienv_set_int_array_region'.
[Mono] Probing 'java_interop_jnienv_set_int_array_region'.
[Mono] Found as 'java_interop_jnienv_set_int_array_region'.
[Mono] DllImport searching in: '__Internal' ('(null)').
[Mono] Searching for 'java_interop_jnienv_get_int_array_region'.
[Mono] Probing 'java_interop_jnienv_get_int_array_region'.
[Mono] Found as 'java_interop_jnienv_get_int_array_region'.
[Mono] Loading reference 3 of Xamarin.Android.Support.v7.AppCompat.dll asmctx DEFAULT, looking for Xamarin.Android.Support.Compat, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
[Mono] Assembly Ref addref Xamarin.Android.Support.v7.AppCompat[0xe02662c0] -> Xamarin.Android.Support.Compat[0xe0265f60]: 5
[Mono] DllImport searching in: '__Internal' ('(null)').
[Mono] Searching for 'java_interop_jnienv_get_float_field'.
[Mono] Probing 'java_interop_jnienv_get_float_field'.
[Mono] Found as 'java_interop_jnienv_get_float_field'.
[mono-rt] /proc/self/maps:
[mono-rt] 12c00000-32c00000 rw-p 00000000 00:01 11957 /dev/ashmem/dalvik-main space (region space) (deleted)
[mono-rt] 5f8a5000-5f8a9000 r-xp 00000000 08:06 331 /system/bin/app_process32
[mono-rt] 5f8aa000-5f8ab000 r--p 00004000 08:06 331 /system/bin/app_process32
[mono-rt] 5f8ab000-5f8ac000 rw-p 00000000 00:00 0
[mono-rt] 70130000-70316000 rw-p 00000000 08:13 105905 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 70316000-703d3000 rw-p 00000000 08:13 105906 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 703d3000-70410000 rw-p 00000000 08:13 105907 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 70410000-70438000 rw-p 00000000 08:13 105908 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 70438000-7043c000 rw-p 00000000 08:13 105909 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 7043c000-7046e000 rw-p 00000000 08:13 105910 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 7046e000-7049c000 rw-p 00000000 08:13 105911 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 7049c000-709d8000 rw-p 00000000 08:13 105912 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 709d8000-70a29000 rw-p 00000000 08:13 105913 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 70a29000-70a31000 rw-p 00000000 08:13 105914 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 70a31000-70a38000 rw-p 00000000 08:13 105915 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 70a38000-70a4d000 rw-p 00000000 08:13 105916 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 70a4d000-70a6b000 rw-p 00000000 08:13 105917 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 70a6b000-70a6c000 rw-p 00000000 08:13 105918 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 70a6c000-70a6f000 rw-p 00000000 08:13 105919 /data/dalvik-cache/x86/system@[email protected]
[mono-rt] 70a6f000-70c4e000 r--p 00000000 08:06 1232 /system/framework/x86/boot.oat
[mono-rt] 70c4e000-712ff000 r-xp 001df000 08:06 1232 /system/framework/x86/boot.oat
[mono-rt] 712ff000-71301000 rw-p 00000000 00:00 0 [anon:.bss]
[mono-rt] 71301000-71302000 r--p 00890000 08:06 1232 /system/framework/x86/boot.oat
[mono-rt] 71302000-71303000 rw-p 00891000 08:06 1232 /system/framework/x86/boot.oat
[mono-rt] 71303000-713dc000 r--p 00000000 08:06 1205 /system/framework/x86/boot-core-libart.oat
[libc] Fatal signal 11 (SIGSEGV), code 1, fault addr 0x50 in tid 2257 (pool-6-thread-2)
mzekrallah
on 8 Apr 2019
This is a pretty big blocker for our enterprise Android app that can not be debugged! Surely this was tested before making VS 2019 GA? Hope it gets fixed ASAP!
crs2m5smith
on 8 Apr 2019
Notes for the soft debugger and runtime engineers about using
sdb and lldb at the same time with the test case
As one way to get debugging symbols for libmonosgen-2.0 on recent Android versions, you can build the app in the shared runtime configuration, add a copy of /Library/Frameworks/Xamarin.Android.framework/Versions/Current/lib/xamarin.android/xbuild/Xamarin/Android/lib/x86/libmonosgen-2.0.d.so to the project, name it lib/x86/libmonosgen-2.0.so, and set it to a build action of AndroidNativeLibrary.
Build and run the app once from Visual Studio for Mac to double-check that the error occurs as expected.
Forward a port from the Android emulator to the local host, for example port 50100:
adb forward tcp:50100 tcp:50100Set a property to tell the Mono runtime to wait for a soft debugger connection on that port during startup:
adb shell setprop debug.mono.extra 'debug=127.0.0.1:50100,timeout=2000000000,loglevel=2,server=y'Launch the application using
xa-lldb:xa-lldb SampleApp.Android.csprojOnce
lldbis attached, set it to ignore a couple signals:proc handle -n false -p true -s false SIGPWR SIGXCPUContinue running the app in
lldb.Attach to the app using
sdb. For example, launchsdb-dev, and then run:connect 127.0.0.1 50100Allow some time for app to load on the emulator, and then proceed with the steps to reproduce.
Additional results with these steps
When the segmentation fault occurs, lldb shows:
* thread #1, name = 'orten.SampleApp', stop reason = jit-debug-register
frame #0: libmonosgen-2.0.so`__mono_jit_debug_register_code at lldb.c:138
thread #19, name = 'Filter', stop reason = signal SIGSEGV: invalid address (fault address: 0x50)
frame #0: libmonosgen-2.0.so`mono_class_vtable_checked(domain=0x00000000, klass=0x9f2d68b8, error=0x88c00658) at object.c:1890
The backtrace of thread 19 is:
* thread #19, name = 'Filter', stop reason = signal SIGSEGV: invalid address (fault address: 0x50)
* frame #0: libmonosgen-2.0.so`mono_class_vtable_checked(domain=0x00000000, klass=0x9f2d68b8, error=0x88c00658) at object.c:1890
frame #1: libmonosgen-2.0.so`get_current_thread_ptr_for_domain(domain=<unavailable>, thread=<unavailable>) at threads.c:595
The backtrace of thread 1 is:
* thread #1, name = 'orten.SampleApp', stop reason = jit-debug-register
* frame #0: libmonosgen-2.0.so`__mono_jit_debug_register_code at lldb.c:138
frame #1: libmonosgen-2.0.so`add_entry(type=<unavailable>, buf=<unavailable>) at lldb.c:308
frame #2: libmonosgen-2.0.so`mono_lldb_save_method_info(cfg=<unavailable>) at lldb.c:546
brendanzagaeski
on 8 Apr 2019
Additional results
The backtrace in my previous comment was from an Android 7.1 (API level 25) x86 emulator. On a Google Pixel 3 Android 9.0 (API level 28) device, the backtrace I get is:
* thread #20, name = 'Filter', stop reason = signal SIGSEGV: invalid address (fault address: 0xbc)
* frame #0: libmonosgen-2.0.so`mono_class_vtable_checked(domain=0x0000000000000000, klass=0x0000007200230648, error=0x00000071e92f9178) at object.c:1890
frame #1: libmonosgen-2.0.so`get_current_thread_ptr_for_domain(domain=0x0000000000000000, thread=0x00000071ebfec508) at threads.c:595
frame #2: libmonosgen-2.0.so`mono_thread_current at threads.c:1939
frame #3: libmonosgen-2.0.so`process_event(event=<unavailable>, arg=<unavailable>, il_offset=<unavailable>, ctx=<unavailable>, events=<unavailable>, suspend_policy=<unavailable>) at debugger-agent.c:3715
frame #4: libmonosgen-2.0.so`thread_end [inlined] process_profiler_event(event=EVENT_KIND_THREAD_DEATH, arg=0x00000071ebfec508) at debugger-agent.c:3875
frame #5: libmonosgen-2.0.so`thread_end(prof=<unavailable>, tid=<unavailable>) at debugger-agent.c:3991
frame #6: libmonosgen-2.0.so`mono_profiler_raise_thread_stopped(tid=<unavailable>) at profiler-events.h:105
frame #7: libmonosgen-2.0.so`mono_thread_detach_internal(thread=<unavailable>) at threads.c:979
frame #8: libmonosgen-2.0.so`thread_detach(info=0x00000071e949a000) at threads.c:3215
frame #9: libmonosgen-2.0.so`unregister_thread(arg=<unavailable>) at mono-threads.c:544
frame #10: libmonosgen-2.0.so`thread_info_key_dtor(arg=0x00000071e949a000) at mono-threads.c:774
frame #11: 0x00000072899c58e8 libc.so`pthread_key_clean_all() + 124
frame #12: 0x00000072899c5374 libc.so`pthread_exit + 76
frame #13: 0x00000072899c5264 libc.so`__pthread_start(void*) + 44
frame #14: 0x000000728996617c libc.so`__start_thread + 72
It feels like the Async Await methods of our applications (I have a few that I've tried) cause it to crash in Debug Mode. I also found the same line as CheezeBarron. Not sure if this helps, but hopefully it does.
[libc] Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xbc in tid 27358 (AsyncTask #5)
clintonrocksmith
on 9 Apr 2019
I'm experiencing something very similar. Just getting started with MvvmCross and my sample application crashes with SIGSEGV after leaving the screen idle for ~30 seconds.
04-09 11:20:31.048 16242-16325/com.accentdesign.xamarinboilerplate E/mono-rt: /proc/self/maps:
04-09 11:20:31.049 16242-16325/com.accentdesign.xamarinboilerplate E/mono-rt: 12c00000-12e17000 rw-p 00000000 00:04 6297 /dev/ashmem/dalvik-main space (deleted)
12e17000-2ac00000 ---p 00217000 00:04 6297 /dev/ashmem/dalvik-main space (deleted)
2ac00000-2ac01000 rw-p 00000000 00:04 6298 /dev/ashmem/dalvik-main space 1 (deleted)
2ac01000-42c00000 ---p 00001000 00:04 6298 /dev/ashmem/dalvik-main space 1 (deleted)
6fc84000-7017c000 rw-p 00000000 fc:00 229392 /data/dalvik-cache/x86/system@[email protected]
7017c000-7025f000 rw-p 00000000 fc:00 229393 /data/dalvik-cache/x86/system@[email protected]
7025f000-7027a000 rw-p 00000000 fc:00 229394 /data/dalvik-cache/x86/system@[email protected]
7027a000-7029d000 rw-p 00000000 fc:00 229395 /data/dalvik-cache/x86/system@[email protected]
7029d000-7029e000 rw-p 00000000 fc:00 229396 /data/dalvik-cache/x86/system@[email protected]
7029e000-702c2000 rw-p 00000000 fc:00 229397 /data/dalvik-cache/x86/system@[email protected]
702c2000-702df000 rw-p 00000000 fc:00 229398 /data/dalvik-cache/x86/system@[email protected]
702df000-706f5000 rw-p 00000000 fc:00 229399 /data/dalvik-cache/x86/system@[email protected]
706f5000-70719000 rw-p 00000000 fc:00 229400 /data/dalvik-cache/x86/system@[email protected]
70719000-7071d000 rw-p 00000000 fc:00 229401 /data/dalvik-cache/x86/system@[email protected]
7071d000-70720000 rw-p 00000000 fc:00 229402 /data/dalvik-cache/x86/system@[email protected]
70720000-70738000 rw-p 00000000 fc:00 229403 /data/dalvik-cache/x86/system@[email protected]
70738000-70749000 rw-p 00000000 fc:00 229404 /data/dalvik-cache/x86/system@[email protected]
70749000-70cbc000 r--p 00000000 fd:00 1001 /system/framework/x86/boot.oat
70cbc000-7107c000 r-xp 00573000 fd:00 1001 /system/framework/x86/boot.oat
7107c000-7107d000 r--p 00933000 fd:00 1001 /system/framework/x86/boot.oat
7107d000-7107e000 rw-p 00934000 fd:00 1001 /system/framework/x86/boot.oat
7107e000-714fe000 r--p 00000000 fd:00 985 /system/framework/x86/boot-core-libart.oat
714fe000-717e7000 r-xp 00480000 fd:00 985 /system/framework/x86/boot-core-libart.oat
717e7000-717e8000 r--p 00769000 fd:00 985 /system/framework/x86/boot-core-libart.oat
717e8000-717e9000 rw-p 0076a000 fd:00 985 /system/framework/x86/boot-core-libart.oat
04-09 11:20:31.049 16242-16325/com.accentdesign.xamarinboilerplate A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x50 in tid 16325 (AsyncTask #1)
04-09 11:20:31.053 16242-16326/com.accentdesign.xamarinboilerplate A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x50 in tid 16326 (AsyncTask #2)
thisdarktao
on 9 Apr 2019
Preliminary verification of candidate fix:
- For x86 emulator, extract
$MSBuild/Xamarin/Android/lib/x86/libmonosgen-2.0.sofrom the.vsixof the public non-commerical build that includes the candidate fix. Push the
libomonosgen-2.0.soto the external.__override__/lib/directory of the test app:adb push '$MSBuild/Xamarin/Android/lib/x86/libmonosgen-2.0.so' '/sdcard/Android/data/com.dotMorten.SampleApp/files/.__override__/lib/libmonosgen-2.0.so'Repeat the test scenario.
Result:
:+1: The app does not crash while debugging from Visual Studio.
brendanzagaeski
on 10 Apr 2019
Preliminary verification of candidate fix:
- For x86 emulator, extract
$MSBuild/Xamarin/Android/lib/x86/libmonosgen-2.0.sofrom the.vsixof the public non-commerical build that includes the candidate fix.- Push the
libomonosgen-2.0.soto the external.__override__/lib/directory of the test app:
adb push '$MSBuild/Xamarin/Android/lib/x86/libmonosgen-2.0.so' '/sdcard/Android/data/com.dotMorten.SampleApp/files/.__override__/lib/libmonosgen-2.0.so'- Repeat the test scenario.
Result:
👍 The app does not crash while debugging from Visual Studio.
thanks ... I used an arm64-v8a version on my device and it also worked!
mapsouza
on 10 Apr 2019
Hello, our team is also experiencing this. I like that mapsouza is offering a preliminary work around but when can we expect this change to be released, and is this released in the form of Xamarin.Forms update or VS for Mac 2019 update --> https://developercommunity.visualstudio.com/content/problem/515603/android-crashes-every-time-with-the-new-vs-for-mac.html
nichojo89
on 11 Apr 2019
Apologies in advance that I don't have precise details about the timeline for publication of the updated Xamarin.Android SDK version as part of Visual Studio. I believe the approximate answer is as soon as possible, but that might be another week or more. To add one more little bit of info to this issue before the weekend, here are links for the candidate development installer packages that include the fix:
- Xamarin.Android.Sdk.9.2.2.1.vsix for Windows
- xamarin.android-9.2.2-1.pkg for macOS
I did a quick sanity-check of these packages myself to verify that I could debug the test case 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.2.0.5, 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.2.0.5 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.2.0.5 in Visual Studio on Windows, navigate to Extensions > Manage Extensions, select the Xamarin.Android SDK entry, and click Revert.
brendanzagaeski
on 13 Apr 2019
Notes for the soft debugger and runtime engineers:
Here's an especially small test scenario for this issue that a user mentioned on the Xamarin forums, in case it might be handy for automated testing or similar.
- Download the test case.
- Start debugging the app from Visual Studio.
- Tap the Button button once the app launches.
I confirmed that this scenario produced the same backtrace I saw previously and verified that the development installer packages with the candidate fix prevented the unexpected exit.
brendanzagaeski
on 13 Apr 2019
Apologies in advance that I don't have precise details about the timeline for publication of the updated Xamarin.Android SDK version as part of Visual Studio. I believe the approximate answer is as soon as possible, but that might be another week or more. To add one more little bit of info to this issue before the weekend, here are links for the candidate development installer packages that include the fix:
* [Xamarin.Android.Sdk.9.2.2.1.vsix](https://xamarin-downloads.azureedge.net/uploads/zqaqax3zm35/Xamarin.Android.Sdk.9.2.2.1.vsix) for Windows * [xamarin.android-9.2.2-1.pkg](https://xamarin-downloads.azureedge.net/uploads/apzrcyz3xhs/xamarin.android-9.2.2-1.pkg) for macOSI did a quick sanity-check of these packages myself to verify that I could debug the test case 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.2.0.5, 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.2.0.5 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.2.0.5 in Visual Studio on Windows, navigate to Extensions > Manage Extensions, select the Xamarin.Android SDK entry, and click Revert.
Thank you, @brendanzagaeski will that fix for android on Mac issue which occurs even if you just run an app in debug mode and after a few seconds (without a single click) crashed
starl1n
on 14 Apr 2019
will that fix for android on Mac issue which occurs even if you just run an app in debug mode and after a few seconds (without a single click) crashed
@starl1n, yes, that sounds like the issue that is addressed by these candidate builds (thanks to the fix from https://github.com/mono/mono/commit/5ac37ccd38582334a6e12210f86b1c3597d5abb2).
If you still see a crash while debugging with these candidate versions, then I'd recommend to collect the adb logcat output from the device (or emulator) during the crash and attach that to a new issue. There is always a small chance that the crash you are seeing in your app might be unrelated to the earlier test cases on this issue. Thanks!
brendanzagaeski
on 15 Apr 2019
@brendanzagaeski
Hi Brendan, could you please provide another link for the Android version? I tried to download it 3 times, but the the download stops each time at 232 MB on 322, and I get then a "Network error".
Thank you!
Goldstrike
on 17 Apr 2019
@brendanzagaeski downgrading to the version link provided has fixed the crash issue for us and we can debug Android. Thank you. Look forward to the VS update that fixes it, but least we aren't sitting ducks now.
@starl1n Yes, the version in link when downloaded will fix that issue
crs2m5smith
on 17 Apr 2019
macOS fix published. The new Xamarin.Android SDK version 9.2.3.0 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.
Windows fix upcoming. Due to an uncommon release cadence match-up, the corresponding update for Visual Studio 2019 is still upcoming. I will update this issue again when that release is available.
brendanzagaeski
on 18 Apr 2019
@brendanzagaeski if I understand you correctly this isn't in 16.0.2 and the vsix posted above doesn't seem to be compatible with VS16.0...
dansiegel
on 19 Apr 2019
this isn't in 16.0.2
Correct, unfortunately. The updated Xamarin.Android SDK with the fix is not yet included in Visual Studio 2019 version 16.0.2. That was a confusing release match-up that happened this time around by a few coincidences.
the vsix posted above doesn't seem to be compatible with VS16.0...
I double-checked the .vsix behavior locally and got it to install on my (maybe too minimal) installation of Visual Studio 2019 version 16.0.2. But I don't have too much background knowledge of how the VSIX installer behaves, so it's definitely possible the scenario I tested doesn't match what most users would see. If you like, you can send a one to one message to me on Gitter, for example using a /query @brendanzagaeski command from within the Xamarin.Android Gitter channel, paste over whatever messages you're getting in the VSIX installer, and I'll take a look!
brendanzagaeski
on 19 Apr 2019
@brendanzagaeski Hey Brendan, I run into the same issue as @Goldstrike. Since the fix is still not in the release channel, could you please provide a different link for the fixed extension?
pikausp
on 24 Apr 2019
@pikausp, you can give this alternative temporary link a try:
Xamarin.Android.Sdk.9.2.2.1.vsix for Windows
That's on the Akamai CDN under my individual Azure account, compared to the previous link that's on the Microsoft CDN under a team Azure account. Since it's on my individual Azure account, I'll turn that link off and edit the link out of this comment after the Visual Studio 2019 version with the fix is available.
EDIT: The Visual Studio 2019 update with the fix is now available, so I have edited out the link. See the later comment for additional information about the Visual Studio 2019 version that contains the fix.
brendanzagaeski
on 25 Apr 2019
Is there any progress on fixing the confusing release match-up?
Happypig375
on 25 Apr 2019
I experienced the issue from first installing VS2019 a couple of days ago. After updating to 16.0.2 and downloading the .vsix for Windows (from the original link but it took 5 attempts) it installed correctly and i can now debug.
simon-wainy
on 25 Apr 2019
I am getting the following errors trying to install the vsix from both links:
25/04/2019 15:56:43 - Microsoft VSIX Installer
25/04/2019 15:56:43 - -------------------------------------------
25/04/2019 15:56:43 - vsixinstaller.exe version:
25/04/2019 15:56:43 - 16.1.42
25/04/2019 15:56:43 - -------------------------------------------
25/04/2019 15:56:43 - Command line parameters:
25/04/2019 15:56:43 - C:program files (x86)microsoft visual studioinstallerresourcesappServiceHubServicesMicrosoft.VisualStudio.Setup.ServiceVSIXInstaller.exe,C:Users\DownloadsXamarin.Android.Sdk.9.2.2.1.vsix
25/04/2019 15:56:43 - -------------------------------------------
25/04/2019 15:56:43 - Microsoft VSIX Installer
25/04/2019 15:56:43 - -------------------------------------------
25/04/2019 15:56:43 - System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
at Microsoft.VisualStudio.Setup.Configuration.ISetupInstance2.GetState()
at VSIXInstaller.SetupExtensions.GetLaunchableInstances(ISetupConfiguration2 configuration)
at VSIXInstaller.SupportedSKUs.EnumerateIsolatedInstalls(Action1 callback)
at VSIXInstaller.SupportedSKUs.AddInstalledLocationBasedSKUs(IntPtr userToken)
at VSIXInstaller.SupportedSKUs.InitializeSupportedSKUs(IntPtr userToken)
at VSIXInstaller.ExtensionService.InitializeSupportedSKUs(ICommandLineData cmdLineData, IntPtr duplicatedUserToken)
at VSIXInstaller.App.Initialize(Boolean isRepairSupported)
at VSIXInstaller.App.Initialize()
at System.Threading.Tasks.Task1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
Have tried multiple downloads of each
rysbilinski
on 25 Apr 2019
@brendanzagaeski thank you. Both, the new link and the extension work.
pikausp
on 25 Apr 2019
Is there any progress on fixing the confusing release match-up?
Apologies in advance that I don't have specific timing information for the publication of the version of Visual Studio 2019 that will include the fix. Barring unexpected complications, it will be included in the next version 16.0.x release. Historically, the time between Visual Studio 2017 version 15.x.x updates was under a month.
As one additional piece of information in case it might be of interest to anyone who uses the preview versions, the new Visual Studio 2019 version 16.1 Preview 2 release from yesterday does include the fix.
brendanzagaeski
on 25 Apr 2019
System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
at Microsoft.VisualStudio.Setup.Configuration.ISetupInstance2.GetState()
@rysbilinski, I haven't debugged errors from ISetupInstance2.GetState() before, so I'm not quite sure what that error would indicate. To make one guess, repairing the Visual Studio installation via the Visual Studio Installer might change the behavior. The ISetupInstance2.GetState() method attempts to determine the overall installation state of the Visual Studio instance.
brendanzagaeski
on 25 Apr 2019
System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
at Microsoft.VisualStudio.Setup.Configuration.ISetupInstance2.GetState()@rysbilinski, I haven't debugged errors from
ISetupInstance2.GetState()before, so I'm not quite sure what that error would indicate. To make one guess, repairing the Visual Studio installation via the Visual Studio Installer might change the behavior. TheISetupInstance2.GetState()method attempts to determine the overall installation state of the Visual Studio instance.
Thanks for the response. Performed a repair and sadly the same issue is appearing.
Going to try the preview version
rysbilinski
on 26 Apr 2019
@brendanzagaeski reinstalled Visual Studio and the issue is fixed! Thanks
rysbilinski
on 27 Apr 2019
so i'm guessing this issue means that no one gets to use xamarin test cloud for testing xamarin builds at microsoft? there's one free device guys /s
kkarakk
on 29 Apr 2019
Serious bugs like these should be given topmost priority, not stay unfixed for 4 days without any indication of when to expect a fix 🙄
I first reported this back in January, a couple of days after preview 2 was released. Someone started looking at it quite quickly but seemed to struggle with repro steps. Sadly I didn't have time back then to try and create a small test application as we were at a critical point in our mobile app development.
AndrueCope
on 30 Apr 2019
Windows fix published. The new Xamarin.Android SDK version 9.2.3.0 that includes the fix for this issue has now been published as part of Visual Studio 2019 version 16.0.3. Check for the latest updates or install the most recent release from https://visualstudio.microsoft.com/downloads/ to get the fix.
brendanzagaeski
on 30 Apr 2019
@brendanzagaeski It looks like this problem (or a very similar one) has re-occurred with VS 16.1.0 (Xamarin.Android 9.3.0.22). Was this fix merged up to 9.3?
EP01
on 22 May 2019
@EP01 , yes the fix for this particular issue is present in the Xamarin.Android 9.3.0.22 as shipped in Visual Studio 2019 version 16.1. (I also did a quick double-check of one of the test cases with that version just now to make sure it still debugged successfully, and it worked correctly.)
That said, I have an initial suspicion that the scope of https://github.com/mono/mono/issues/14170 (listed as a known issue in the Xamarin.Android 9.3 release notes) 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. Another user has reported a similar behavior in https://github.com/xamarin/xamarin-android/issues/3112, so I'll recommend to continue the conversation there to help figure out what is happening in this new scenario. Thanks!
brendanzagaeski
on 22 May 2019
same issue for visual studio 16.1.1 and 16.2.0 preview 1 versions.
download the 16.0.3 and not problem.
https://docs.microsoft.com/en-us/visualstudio/releases/2019/history
hasanoruc
on 26 May 2019
@brendanzagaeski how can i download visual studio 16.0.3 community version?
hasanoruc
on 26 May 2019
Does Xamarin even test serious bugs like these?
Happypig375
on 27 May 2019
I can confirm that I am getting the same problem for Visual Studio Version 16.1.1.
SpiegelSoft
on 27 May 2019
how can i download visual studio 16.0.3 community version?
I believe the previous version downloads are only available for Professional and higher editions. That said, there is a possible approach to downgrade just the Xamarin.Android SDK by some manual file copying in the Community edition. See https://github.com/xamarin/xamarin-android/issues/3112#issuecomment-495780758 for additional details.
For other users seeing a similar behavior as this issue (https://github.com/xamarin/xamarin-android/issues/2920) in Visual Studio 2019 version 16.1 or higher, I'll recommend to switch over to following https://github.com/xamarin/xamarin-android/issues/3112 for further updates. It turns out the crash in Visual Studio 2019 version 16.1 has a different cause and can happen with or without the debugger attached.
brendanzagaeski
on 28 May 2019
I might have some additional info, recently due to Android requiring to go to 64bits as in a few months I ran into a similiar problem.
When the App Architecture is changed from "armeabi-v7a" to "arm64-v8a" it throws me a very simliliar errors.
When logging in using Microsoft.Azure.Mobile.Client through a async UI thread it will work. It will only crash when the request hits a timeout.
Additional info:
- VS 2019 16.1.1
- Xamarin Forms v4.0.0.425677
- Microsoft.Azure.Mobile.Client v4.1.1
Code:
JObject loginData = new JObject(new JProperty("username", username), new JProperty("password", password), new JProperty("installationID", Client.GetPush().InstallationId));
try
{
--> MobileServiceUser user = await Client.LoginAsync("custom", loginData); <--
CrossSecureStorage.Current.SetValue(Constants.TokenKey, user.MobileServiceAuthenticationToken);
CrossSecureStorage.Current.SetValue(Constants.UserKey, user.UserId);
CrossSecureStorage.Current.SetValue(Constants.UsernameKey, username);
CrossSecureStorage.Current.SetValue(Constants.PasswordKey, password);
}
Stack traces:
=================================================================
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.
=================================================================
05-29 10:49:48.529 E/mono-rt ( 8027): /proc/self/maps:
=================================================================
Basic Fault Adddress Reporting
=================================================================
Memory around native instruction pointer (0x7b47bfd678):0x7b47bfd668 00 1c 40 b9 c0 03 5f d6 fd 7b bf a9 fd 03 00 91 ..@..._..{......
0x7b47bfd678 08 20 40 b9 a8 00 c8 37 88 01 e0 37 00 00 40 f9 . @....7...7..@.
0x7b47bfd688 fd 7b c1 a8 c0 03 5f d6 60 08 00 b0 01 0a 00 f0 .{...._.`05-29 10:49:48.529 E/mono-rt ( 8027): 12c00000-52c00000 rw-p 00000000 00:01 16946 /dev/ashmem/dalvik-main space (region space) (deleted)
05-29 10:49:48.529 E/mono-rt ( 8027): 6ff5a000-70202000 rw-p 00000000 103:08 905 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.529 E/mono-rt ( 8027): 70202000-70308000 rw-p 00000000 103:08 912 /data/dalvik-cache/arm64/system@[email protected].......
0x7b47bfd698 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>
=================================================================
05-29 10:49:48.530 E/mono-rt ( 8027): 70308000-70352000 rw-p 00000000 103:08 923 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70352000-70388000 rw-p 00000000 103:08 934 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70388000-7038c000 rw-p 00000000 103:08 940 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 7038c000-703cf000 rw-p 00000000 103:08 942 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 703cf000-7040a000 rw-p 00000000 103:08 962 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 7040a000-70bf7000 rw-p 00000000 103:08 964 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70bf7000-70c83000 rw-p 00000000 103:08 970 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70c83000-70c8c000 rw-p 00000000 103:08 973 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70c8c000-70c95000 rw-p 00000000 103:08 975 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70c95000-70cb9000 rw-p 00000000 103:08 977 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70cb9000-70ce1000 rw-p 00000000 103:08 978 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70ce1000-70ce2000 rw-p 00000000 103:08 979 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70ce2000-70ce5000 rw-p 00000000 103:08 980 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70ce5000-70d70000 rw-p 00000000 103:08 981 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70d70000-70d97000 rw-p 00000000 103:08 982 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70d97000-70dd0000 rw-p 00000000 103:08 984 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70dd0000-70dd2000 rw-p 00000000 103:08 986 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70dd2000-70dd3000 rw-p 00000000 103:08 988 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70dd3000-70dd9000 rw-p 00000000 103:08 989 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70dd9000-70ddf000 rw-p 00000000 103:08 991 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70ddf000-70de4000 rw-p 00000000 103:08 993 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.530 E/mono-rt ( 8027): 70de4000-70deb000 rw-p 00000000 103:08 995 /data/dalvik-cache/arm64/system@[email protected]
05-29 10:49:48.533 F/libc ( 8027): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 8167 (Thread Pool Wor)
=================================================================
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.
=================================================================
05-29 09:57:13.076 E/mono-rt ( 4449): /proc/self/maps:
=================================================================
Basic Fault Adddress Reporting
=================================================================
Memory around native instruction pointer (0x7b47bb7678):0x7b47bb7668 00 1c
05-29 09:57:13.076 E/mono-rt ( 4449): 12c00000-52c00000 rw-p 00000000 00:01 16946 /dev/ashmem/dalvik-main space (region space) (deleted)
05-29 09:57:13.076 E/mono-rt ( 4449): 6ff5a000-70202000 rw-p 00000000 103:08 905 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.076 E/mono-rt ( 4449): 70202000-70308000 rw-p 00000000 103:08 912 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.076 E/mono-rt ( 4449): 70308000-70352000 rw-p 00000000 103:08 923 /data/dalvik-cache/arm64/system@[email protected]
40 b9 c0 03 5f d6 fd 7b bf a9 fd 03 00 91 ..@..._..{......
0x7b47bb7678 08 20 40 b9 a8 00 c8 37 88 01 e0 37 00 00 40 f9 . @....7...7..@.
0x7b47bb7688 fd 7b c1 a8 c0 03 5f d6 60 08 00 b0 01 0a 00 f0 .{...._.`.......
0x7b47bb7698 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:
=================================================================
=================================================================05-29 09:57:13.076 E/mono-rt ( 4449): 70352000-70388000 rw-p 00000000 103:08 934 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.076 E/mono-rt ( 4449): 70388000-7038c000 rw-p 00000000 103:08 940 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.076 E/mono-rt ( 4449): 7038c000-703cf000 rw-p 00000000 103:08 942 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.076 E/mono-rt ( 4449): 703cf000-7040a000 rw-p 00000000 103:08 962 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.076 E/mono-rt ( 4449): 7040a000-70bf7000 rw-p 00000000 103:08 964 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.076 E/mono-rt ( 4449): 70bf7000-70c83000 rw-p 00000000 103:08 970 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.076 E/mono-rt ( 4449): 70c83000-70c8c000 rw-p 00000000 103:08 973 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.076 E/mono-rt ( 4449): 70c8c000-70c95000 rw-p 00000000 103:08 975 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.076 E/mono-rt ( 4449): 70c95000-70cb9000 rw-p 00000000 103:08 977 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.076 E/mono-rt ( 4449): 70cb9000-70ce1000 rw-p 00000000 103:08 978 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.076 E/mono-rt ( 4449): 70ce1000-70ce2000 rw-p 00000000 103:08 979 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.077 E/mono-rt ( 4449): 70ce2000-70ce5000 rw-p 00000000 103:08 980 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.077 E/mono-rt ( 4449): 70ce5000-70d70000 rw-p 00000000 103:08 981 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.077 E/mono-rt ( 4449): 70d70000-70d97000 rw-p 00000000 103:08 982 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.077 E/mono-rt ( 4449): 70d97000-70dd0000 rw-p 00000000 103:08 984 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.077 E/mono-rt ( 4449): 70dd0000-70dd2000 rw-p 00000000 103:08 986 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.077 E/mono-rt ( 4449): 70dd2000-70dd3000 rw-p 00000000 103:08 988 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.077 E/mono-rt ( 4449): 70dd3000-70dd9000 rw-p 00000000 103:08 989 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.077 E/mono-rt ( 4449): 70dd9000-70ddf000 rw-p 00000000 103:08 991 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.077 E/mono-rt ( 4449): 70ddf000-70de4000 rw-p 00000000 103:08 993 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.077 E/mono-rt ( 4449): 70de4000-70deb000 rw-p 00000000 103:08 995 /data/dalvik-cache/arm64/system@[email protected]
05-29 09:57:13.080 F/libc ( 4449): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x20 in tid 4449 (t365.trifact365)
ThePizzaguy
on 29 May 2019
Hi Brendan,
Can tot provide us information when this bug will be fixed? Very strange that this problem is back again in version 16.1.1
Thanks, Marcel
Outlook voor Android downloadenhttps://aka.ms/ghei36
From: Brendan Zagaeski notifications@github.com
Sent: Tuesday, May 28, 2019 12:08:43 AM
To: xamarin/xamarin-android
Cc: marcelbeeker; Comment
Subject: Re: [xamarin/xamarin-android] App crashes with debugger attached (#2920)
how can i download visual studio 16.0.3 community version?
I believe the previous version downloads are only available for Professional and higher editions. That said, there is a possible approach to downgrade just the Xamarin.Android SDK by some manual file copying in the Community edition. See #3112 (comment)https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fxamarin%2Fxamarin-android%2Fissues%2F3112%23issuecomment-495780758&data=02%7C01%7C%7C5dc7a13be8ab4703cc1208d6e2efe238%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636945917244502631&sdata=dfwUZvi3wNcndBbuGxM10qTOm4H05ahPcuYqDUI1VRY%3D&reserved=0 for additional details.
For other users seeing a similar behavior as this issue (#2920https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fxamarin%2Fxamarin-android%2Fissues%2F2920&data=02%7C01%7C%7C5dc7a13be8ab4703cc1208d6e2efe238%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636945917244512648&sdata=B1V5Npb6Yzr4OWz4ZefgVcdeCNOLMnurwVP2NQBoFLg%3D&reserved=0) in Visual Studio 2019 version 16.1 or higher, I'll recommend to switch over to following #3112https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fxamarin%2Fxamarin-android%2Fissues%2F3112&data=02%7C01%7C%7C5dc7a13be8ab4703cc1208d6e2efe238%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636945917244532652&sdata=YkgOx34Mu91OeUWgHJaKhbaBnZP25pmuquca6mLnMDY%3D&reserved=0 for further updates. It turns out the crash in Visual Studio 2019 version 16.1 has a different cause and can happen with or without the debugger attached.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fxamarin%2Fxamarin-android%2Fissues%2F2920%3Femail_source%3Dnotifications%26email_token%3DAENYSNW2LEXMU5QE6G4TQ5TPXRLWXA5CNFSM4HDLNA72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWKSE5Y%23issuecomment-496312951&data=02%7C01%7C%7C5dc7a13be8ab4703cc1208d6e2efe238%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636945917244542663&sdata=Ud%2B8pA8jYKmRt3sFIZkJ3u8eWms31pjTy4Mps4NUs1k%3D&reserved=0, or mute the threadhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAENYSNVITPTMVISWUPNC36DPXRLWXANCNFSM4HDLNA7Q&data=02%7C01%7C%7C5dc7a13be8ab4703cc1208d6e2efe238%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636945917244552680&sdata=RQ2Ndc%2FGdt3lM4bjvaQFFKspzFumACVbUc3beuMaXJM%3D&reserved=0.
marcelbeeker
on 4 Jun 2019
People, is this bug ever going to be fixed?
I have VS 16.1.1 and my project still crashes with SQLite.
NickeManarin
on 5 Jun 2019
The best place to follow for additional information about the problem in Visual Studio 2019 version 16.1 and higher is: https://github.com/xamarin/xamarin-android/issues/3112 (or the corresponding item on Developer Community).
For example, I'll make sure those issues are switched to the closed state when a version of Visual Studio 2019 version 16.1 with a fix for the issue is released, so you'll be able to watch for the state change to get a notification. There is a candidate change in progress to resolve the issue.
(For additional background context, the crash in Visual Studio 2019 version 16.1 has a new unrelated cause, and can happen with or without the debugger attached.)
brendanzagaeski
on 5 Jun 2019
This evening, I received update 16.1.2 from VS2019. My problem is solved now. I can debug my Xamarin application again in VS2019!
Verzonden vanuit Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 voor Windows 10
Van: Brendan Zagaeski notifications@github.com
Verzonden: Wednesday, June 5, 2019 5:37:17 PM
Aan: xamarin/xamarin-android
CC: marcelbeeker; Comment
Onderwerp: Re: [xamarin/xamarin-android] App crashes with debugger attached (#2920)
The best place to follow for additional information about the problem in Visual Studio 2019 version 16.1 and higher is: #3112https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fxamarin%2Fxamarin-android%2Fissues%2F3112&data=02%7C01%7C%7Cdb4f43768894463f686108d6e9cbb165%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636953458391778291&sdata=ETWwSxzIMMsXrgjDJH2hVqTiAvie3GnOH7yzhv%2BUuos%3D&reserved=0 (or the corresponding item on Developer Communityhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdevelopercommunity.visualstudio.com%2Fcontent%2Fproblem%2F580820%2Fxamarin-problem-following-update-to-vs2019-161.html&data=02%7C01%7C%7Cdb4f43768894463f686108d6e9cbb165%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636953458391788297&sdata=6r2Pj3ix5yuJCZtO8YRWpqaqW1U2wjvKn4EMgQFWRNc%3D&reserved=0).
For example, I'll make sure those issue are switched to the closed state when a version of Visual Studio 2019 version 16.1 with a fix for the issue is released, so you'll be able to watch for the state change to get a notification. There is a candidate change in progress to resolve the issue.
(For additional background context, the crash in Visual Studio 2019 version 16.1 has a new unrelated cause, and can happen with or without the debugger attached.)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fxamarin%2Fxamarin-android%2Fissues%2F2920%3Femail_source%3Dnotifications%26email_token%3DAENYSNQWQ7DB4YO57MF4YJLPY7MS3A5CNFSM4HDLNA72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXADRWA%23issuecomment-499136728&data=02%7C01%7C%7Cdb4f43768894463f686108d6e9cbb165%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636953458391798308&sdata=cE8ziEfGHfgecmFB5OOr3Ey%2BQhDTXTuswB6CTWVGDf4%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAENYSNUORS4OCYOHH323O5TPY7MS3ANCNFSM4HDLNA7Q&data=02%7C01%7C%7Cdb4f43768894463f686108d6e9cbb165%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636953458391808314&sdata=tXYHI8b1apAtIEiDKahDNL2YVmcCdnA67%2FespEcpTLA%3D&reserved=0.
marcelbeeker
on 5 Jun 2019
Guys, the problem is resolved for debugging (in 16.1.2 and 16.1.3) on the main thread, but I am reproducing it randomly when debugging background threads.
06-14 11:36:24.504 E/mono-rt (27806): /proc/self/maps:
=================================================================
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-14 11:36:24.504 E/mono-rt (27806): 12c00000-52c00000 rw-p 00000000 00:01 36406 /dev/ashmem/dalvik-main space (region space) (deleted) Basic Fault Adddress Reporting
=================================================================
Memory around native instruction pointer (0xc9700b20):0xc9700b10 d0 1f 1e 00 70 1f 1e 00 10 00 90 e5 1e ff 2f e1 ....p........./.
0xc9700b20 08 00 90 e5 1e ff 2f e1 04 00 90 e5 1e ff 2f e1 ....../......./.
0xc9700b30 b0 20 d0 e1 00 10 a0 e1 01 00 a0 e3 01 0b 12 e3 . ..............
0xc9700b40 1e ff 2f 11 b2 10 d1 e1 03 30 01 e3 03 00 11 e1 ../......0......
No native Android stacktrace (see debuggerd output).
=================================================================
Managed Stacktrace:
=================================================================
=================================================================
06-14 11:36:24.505 E/mono-rt (27806): 6f266000-6f44c000 rw-p 00000000 fd:01 432572 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.505 E/mono-rt (27806): 6f44c000-6f509000 rw-p 00000000 fd:01 432575 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.505 E/mono-rt (27806): 6f509000-6f547000 rw-p 00000000 fd:01 432577 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.505 E/mono-rt (27806): 6f547000-6f570000 rw-p 00000000 fd:01 432579 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.505 E/mono-rt (27806): 6f570000-6f574000 rw-p 00000000 fd:01 432581 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.505 E/mono-rt (27806): 6f574000-6f5a6000 rw-p 00000000 fd:01 432583 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.505 E/mono-rt (27806): 6f5a6000-6f5d4000 rw-p 00000000 fd:01 432585 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.506 E/mono-rt (27806): 6f5d4000-6fb86000 rw-p 00000000 fd:01 432587 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.506 E/mono-rt (27806): 6fb86000-6fc13000 rw-p 00000000 fd:01 432589 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.506 E/mono-rt (27806): 6fc13000-6fc1b000 rw-p 00000000 fd:01 432591 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.506 E/mono-rt (27806): 6fc1b000-6fc23000 rw-p 00000000 fd:01 432594 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.506 E/mono-rt (27806): 6fc23000-6fc38000 rw-p 00000000 fd:01 432595 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.506 E/mono-rt (27806): 6fc38000-6fc56000 rw-p 00000000 fd:01 432597 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.506 E/mono-rt (27806): 6fc56000-6fc57000 rw-p 00000000 fd:01 432599 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.507 E/mono-rt (27806): 6fc57000-6fc5a000 rw-p 00000000 fd:01 432601 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.507 E/mono-rt (27806): 6fc5a000-6fc69000 rw-p 00000000 fd:01 432603 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.507 E/mono-rt (27806): 6fc69000-6fc6a000 rw-p 00000000 fd:01 432605 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.507 E/mono-rt (27806): 6fc6a000-6fc6b000 rw-p 00000000 fd:01 432607 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.507 E/mono-rt (27806): 6fc6b000-6fc6d000 rw-p 00000000 fd:01 432609 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.507 E/mono-rt (27806): 6fc6d000-6fc72000 rw-p 00000000 fd:01 432611 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.507 E/mono-rt (27806): 6fc72000-6fc73000 rw-p 00000000 fd:01 432613 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.508 E/mono-rt (27806): 6fc73000-6fc7a000 rw-p 00000000 fd:01 432615 /data/dalvik-cache/arm/system@[email protected]
06-14 11:36:24.508 E/mono-rt (27806): 6fc7a000-6fe4b000 r--p 00000000 fd:00 4240 /system/framework/arm/boot.oat
06-14 11:36:24.508 E/mono-rt (27806): 6fe4b000-70446000 r-xp 001d1000 fd:00 4240 /system/framework/arm/boot.oat
06-14 11:36:24.521 F/libc (27806): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x8 in tid 27832 (Debugger agent)
Step request failed: Exception of type 'Mono.Debugger.Soft.VMDisconnectedException' was thrown.
Reproduced with:
Microsoft Visual Studio Community 2019
Version 16.1.3
VisualStudio.16.Release/16.1.3+29009.5
Microsoft .NET Framework
Version 4.7.03062
Installed Version: Community
Xamarin.Android SDK 9.3.0.22 (HEAD/8e7764fdf)
georgi8706
on 14 Jun 2019
Thanks for the information georgi8706, and thanks for the new corresponding report in https://github.com/xamarin/xamarin-android/issues/3222! That behavior where the "Debugger agent" thread is the source of the SIGSEGV looks like it might have a different underlying cause. We'll continue to investigate in https://github.com/xamarin/xamarin-android/issues/3222.
brendanzagaeski
on 18 Jun 2019
Related issues
NatElkins
·
4Comments
sgong-pdftron
·
4Comments
KSemenenko
·
3Comments
sdebruyn
·
3Comments
lin-zy1229
·
3Comments
Most helpful comment
Serious bugs like these should be given topmost priority, not stay unfixed for 4 days without any indication of when to expect a fix 🙄