Bug 60671 - mono-rt random crashes - after updating packages
Summary: mono-rt random crashes - after updating packages
Status: RESOLVED ANSWERED
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Alexander Köplinger [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2017-11-14 14:36 UTC by Rabih harb
Modified: 2017-11-15 14:31 UTC (History)
2 users (show)

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


Attachments
full log output (109.20 KB, text/plain)
2017-11-14 14:36 UTC, Rabih harb
Details


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

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

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


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

Related Links:
Status:
RESOLVED ANSWERED

Description Rabih harb 2017-11-14 14:36:29 UTC
Created attachment 25696 [details]
full log output

dears;

using VS:7.2.2
mono: 5.4.1.6

my Xamarin form android application started having random crashes, no code changes same version working on IOS,
please find below the stack trace, no indication or clues what so ever, please help (see attached for the full log):

---------------------------


[cr_BrowserStartup] Initializing chromium process, singleProcess=true
[cr_media] Requires BLUETOOTH permission
[cr_DRP] No DRP key due to exception:java.lang.ClassNotFoundException: com.android.webview.chromium.Drp
[cr_AwContents] onDetachedFromWindow called when already detached. Ignoring
[cr_AwContents] onDetachedFromWindow called when already detached. Ignoring
[cr_AwContents] onDetachedFromWindow called when already detached. Ignoring
[cr_AwContents] onDetachedFromWindow called when already detached. Ignoring
[cr_AwContents] onDetachedFromWindow called when already detached. Ignoring
[cr_AwContents] onDetachedFromWindow called when already detached. Ignoring
[cr_AwContents] onDetachedFromWindow called when already detached. Ignoring
[cr_AwContents] onDetachedFromWindow called when already detached. Ignoring
[cr_AwContents] onDetachedFromWindow called when already detached. Ignoring
[cr_AwContents] onDetachedFromWindow called when already detached. Ignoring
[art] JNI RegisterNativeMethods: attempt to register 0 native methods for md54ada4fbe4a5955f6151fa282d30cfc48.SelfDisposingBitmapDrawable
[Choreographer] Skipped 67 frames!  The application may be doing too much work on its main thread.
[art] JNI RegisterNativeMethods: attempt to register 0 native methods for md5b60ffeb829f638581ab2bb9b1a7f4f3f.CellRenderer_RendererHolder
[View] requestLayout() improperly called by md5b60ffeb829f638581ab2bb9b1a7f4f3f.ScrollViewContainer{23953ea V.E...... ......ID 0,0-480,3557} during layout: running second layout pass
[View] requestLayout() improperly called by md5270abb39e60627f0f200893b490a1ade.NavigationPageRenderer{632c88a V.E...... ......ID 0,0-480,764 #9} during second layout pass: posting in next frame
[art] Starting a blocking GC Explicit
[art] Explicit concurrent mark sweep GC freed 1145(49KB) AllocSpace objects, 5(100KB) LOS objects, 20% free, 15MB/19MB, paused 506us total 7.972ms
[art] Starting a blocking GC Explicit
[art] Explicit concurrent mark sweep GC freed 21(3KB) AllocSpace objects, 0(0B) LOS objects, 20% free, 15MB/19MB, paused 542us total 8.920ms
[google-breakpad] ### ### ### ### ### ### ### ### ### ### ### ### ###
[google-breakpad] Chrome build fingerprint:
[google-breakpad] 1.0.1
[google-breakpad] 1
[google-breakpad] ### ### ### ### ### ### ### ### ### ### ### ### ###
[mono-rt] Stacktrace:
[mono-rt] 
[mono-rt] /proc/self/maps:
[mono-rt] 12c00000-12e08000 rw-p 00000000 00:04 8227                               /dev/ashmem/dalvik-main space (deleted)
[mono-rt] 12e08000-12f24000 rw-p 00208000 00:04 8227                               /dev/ashmem/dalvik-main space (deleted)
[mono-rt] 12f24000-1ec00000 ---p 00324000 00:04 8227                               /dev/ashmem/dalvik-main space (deleted)
.....
[mono-rt] 7ffff0d4c000-7ffff0d4c000 ---p 00000000 00:00 0 
[mono-rt] 7ffff0d4c000-7ffff154b000 rw-p 00000000 00:00 0                          [stack]
[mono-rt] 7ffff159f000-7ffff15a1000 r-xp 00000000 00:00 0                          [vdso]
[mono-rt] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
[mono-rt] 
[mono-rt] No native Android stacktrace (see debuggerd output).
[mono-rt] 
[mono-rt] 
[mono-rt] =================================================================
[mono-rt] Got a SIGSEGV while executing native code. This usually indicates
[mono-rt] a fatal error in the mono runtime or one of the native libraries 
[mono-rt] used by your application.
[mono-rt] =================================================================
[mono-rt] 
[libc] Fatal signal 11 (SIGSEGV), code 128, fault addr 0x0 in tid 3804 (Finalizer)
--------------------
many thanks in advance !

best, 
rabih
Comment 1 Jon Douglas [MSFT] 2017-11-14 17:03:25 UTC
Hi Rabih,

Thank you for the report! For us to further investigate the cause of this issue, can you please include the following information?

1. Steps to reproduce this, or a reproduction project
2. Your version information found at Help -> About Visual Studio -> Copy Info on Windows or Visual Studio -> About Visual Studio if on a Mac. Given the current information I would assume this is happening on a Mac via the 7.2.2 version.

If you need assistance in adding further details, we have a handy bug writing guide that you can follow:

https://bugzilla.xamarin.com/page.cgi?id=bug-writing.html

Given that this is a SIGSEGV (Segmentation Fault), it may be worth trying other Garbgage Collection Bridge options to see if this is a potential bug in Tarjan which is the default.

https://developer.xamarin.com/guides/android/advanced_topics/garbage_collection/#GC_Bridge_Options

You will then additionally want to include GC_Bridge logging and bridge accounting to help pinpoint this failure.

Thanks in advance!
Comment 2 Rabih harb 2017-11-15 09:41:19 UTC
hello Jon;

thank you for taking the time to reply, much appreciated.
my problem is with the Android version, I recently updated the packages and all went downhill from there.

am suspecting the following packages:
FFimageloading 2.2.25
SQLITE PCL_basic 0.86

below is my IDE info:
----------------
Visual Studio Community 2017 for Mac
Version 7.2.2 (build 11)
Installation UUID: 9bf4b7e5-a4c3-4b42-bee7-ba6f12761daa
Runtime:
	Mono 5.4.1.6 (2017-06/1f4613aa1ac) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 504010006

NuGet
Version: 4.3.1.4445

.NET Core
Runtime: /usr/local/share/dotnet/dotnet
Runtime Versions:
	1.1.1
	1.0.4
SDK: /usr/local/share/dotnet/sdk/1.0.3/Sdks
SDK Version: 1.0.3
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/5.4.1/lib/mono/msbuild/15.0/bin/Sdks

Xamarin.Profiler
Version: 1.5.6
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

Apple Developer Tools
Xcode 9.0 (13247)
Build 9A235

Xamarin.iOS
Version: 11.3.0.47 (Visual Studio Community)
Hash: 51128b8c
Branch: xcode9.1
Build date: 2017-10-31 22:42:13-0400

Xamarin.Android
Version: 8.0.2.1 (Visual Studio Community)
Android SDK: /Users/Rabih/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		6.0 (API level 23)
		7.0 (API level 24)
		7.1 (API level 25)
		8.0 (API level 26)

SDK Tools Version: 26.1.1
SDK Platform Tools Version: 26.0.2
SDK Build Tools Version: 27.0.1
-------------------
I need to turn on native debugging, the problems happen randomly, no while loading a page or onlick, its something happening in the background of the app.

am sorry am not providing any useful info ill check the Garbgage Collection Bridge options

many thanks
Best,
rabih
Comment 3 Rabih harb 2017-11-15 14:31:59 UTC
Hello Jon;


it was the SQLite library, the new updated version was causing this weird behavior,
it happens also on IPHONE, but it's not a fatal error I saw something in the logs, 
that points it out,
 
the error happened when the page resources are garbage collected. long after u visit the content page. it wasn't.

ill close this error, and a heads up for people who might face something similar.
many thanks