Bug 22776 - Fatal Crash on devices with firmware update
Summary: Fatal Crash on devices with firmware update
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 4.18.0
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2014-09-09 10:12 UTC by JohanO
Modified: 2017-06-27 19:33 UTC (History)
3 users (show)

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

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

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

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


Please create a new report 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 NOT_REPRODUCIBLE

Description JohanO 2014-09-09 10:12:13 UTC
Hi guys,

Some of my customers are experiencing this nastiness on startup. What is it about?

 E/﹕ Device driver API match
    Device driver API version: 23
    User space API version: 23
08-08 12:22:37.474  13810-13810/? E/﹕ mali: REVISION=Linux-r3p2-01rel3 BUILD_DATE=Wed Oct  9 21:05:57 KST 2013
08-08 12:22:37.539  13810-13810/? D/OpenGLRenderer﹕ Enabling debug mode 0
08-08 12:22:37.544  13810-13810/? D/ProgressBar﹕ updateDrawableBounds: left = 0
08-08 12:22:37.544  13810-13810/? D/ProgressBar﹕ updateDrawableBounds: top = 0
08-08 12:22:37.544  13810-13810/? D/ProgressBar﹕ updateDrawableBounds: right = 50
08-08 12:22:37.544  13810-13810/? D/ProgressBar﹕ updateDrawableBounds: bottom = 50
08-08 12:22:37.544    2346-2853/? E/EnterpriseContainerManager﹕ ContainerPolicy Service is not yet ready!!!
08-08 12:22:37.544    2346-2853/? D/EnterpriseDeviceManager﹕ ContainerId: 0
08-08 12:22:37.544    2346-2542/? W/LicenseLogService﹕ log() is called by non admin
08-08 12:22:37.574  13810-13810/? E/mono-rt﹕ Stacktrace:
08-08 12:22:37.574  13810-13810/? E/mono-rt﹕ =================================================================
    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.
    =================================================================
08-08 12:22:37.574  13810-13810/? A/libc﹕ Fatal signal 11 (SIGSEGV) at 0x47242024 (code=2), thread 13810 (novage.Monovage)
08-08 12:22:37.634  13810-13810/? E/mono﹕ Unhandled Exception:
    System.NullReferenceException: Object reference not set to an instance of an object
08-08 12:22:37.634  13810-13810/? E/mono-rt﹕ [ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
08-08 12:22:37.654    1933-2189/? I/SurfaceFlinger﹕ id=191 Removed TplashScree (1/5)
08-08 12:22:37.654    1933-2042/? I/SurfaceFlinger﹕ id=191 Removed TplashScree (-2/5)
08-08 12:22:37.654    1933-1933/? I/SurfaceFlinger﹕ id=191 Removed TplashScree (-2/5)
08-08 12:22:37.654    2346-7205/? I/ActivityManager﹕ Process Monovage.Monovage (pid 13810) (adj 0) has died.
08-08 12:22:37.654    2346-7205/? W/ActivityManager﹕ Force removing ActivityRecord{43157990 u0 Monovage.Monovage/monovage.SplashScreenActivity}: app died, no saved state
08-08 12:22:37.659    1933-2189/? I/SurfaceFlinger﹕ id=190 Removed Nonovage (3/4)
08-08 12:22:37.659    1933-2042/? I/SurfaceFlinger﹕ id=190 Removed Nonovage (-2/4)
08-08 12:22:37.674    1933-2001/? I/SurfaceFlinger﹕ id=192 createSurf (720x1280),1 flag=4, Mauncher
08-08 12:22:37.679    2346-2461/? D/STATUSBAR-StatusBarManagerService﹕ manageDisableList what=0x0 pkg=WindowManager.LayoutParams
08-08 12:22:37.704    2346-7205/? D/WindowManager﹕ computeScreenConfigurationLocked() set config.orientation=1 dw=720 dh=1280 Callers=com.android.server.wm.WindowManagerService.updateOrientationFromAppTokensLocked:5171 com.android.server.wm.WindowManagerService.updateOrientationFromAppTokens:5142 com.android.server.am.ActivityStack.resumeTopActivityLocked:2776
08-08 12:22:37.704    2346-7205/? D/PowerManagerService﹕ setKeyboardVisibility: false
08-08 12:22:37.714    2606-2606/? D/STATUSBAR-NetworkController﹕ onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
08-08 12:22:37.729  13769-13769/? I/DEBUG﹕ unexpected waitpid response: n=13810, status=00000100
08-08 12:22:37.729  13769-13769/? I/DEBUG﹕ ptrace detach from 13810 failed: No such process
08-08 12:22:37.729  13769-13769/? I/DEBUG﹕ debuggerd committing suicide to free the zombie!
08-08 12:22:37.729    1934-1934/? D/Zygote﹕ Process 13810 exited cleanly (1)
08-08 12:22:37.734  13841-13841/? I/DEBUG﹕ debuggerd: Feb 25 2014 15:39:33
08-08 12:22:37.774    2750-2750/? D/AbsListView﹕ unregisterIRListener() is called
08-08 12:22:37.774    2750-2750/? D/AbsListView﹕ unregisterIRListener() is called
08-08 12:22:37.774    2346-3233/? E/EnterpriseContainerManager﹕ ContainerPolicy Service is not yet ready!!!
08-08 12:22:37.774    2346-3233/? D/EnterpriseDeviceManager﹕ ContainerId: 0
08-08 12:22:37.779    2346-2542/? W/LicenseLogService﹕ log() is called by non admin
08-08 12:22:37.779    2346-3233/? W/InputMethodManagerService﹕ Got RemoteException sending setActive(false) notification to pid 13810 uid 10014
08-08 12:22:37.794    2750-2750/? D/comsamsunglog﹕ [MSC_HERO_Accu_JB]>>> ====================================================================================================================
Comment 1 Jatin 2014-09-12 02:45:29 UTC
Hi,

Could you please provide us the test steps you followed. 

Also can you please add the logs from the following places?:

On XS IDE Log  Location: XS>Help> Open Log Directory> IDE.log file (with latest timestamp)

AndroidTools log: XS->Help->Open Log Directory->AndroidTools.log

Also the environment details, i.e. (version of Xamarin Studio and Xamarin.Android and Mono Framework version): XS>About Xamarin Studio>Show Details>Copy information.
Comment 2 JohanO 2014-09-16 02:16:30 UTC
Hi, Sorry about the delayed response. I don't really have this information because it happened on a customer's phone who graciously activated development mode on his phone and sent me the log.

As far as XS - I am using the latest Android API + XS 5.3 (build 441) But here's a dump from XS

=== Xamarin Studio ===

Version 5.3 (build 441)
Installation UUID: 1a451b84-294e-4206-86ac-ec83dc16bb0e
Runtime:
	Mono 3.8.0 ((no/45d0ba1)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 308000009

=== Apple Developer Tools ===

Xcode 5.1.1 (5085)
Build 5B1008

=== Xamarin.Mac ===

Version:

=== Xamarin.Android ===

Version: 4.14.0 (Business Edition)
Android SDK: /Users/johanotto 1/Library/Developer/Xamarin/android-sdk-mac_x86
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.4    (API level 19)
		4.4.87 (API level 20)
		4.5    (API level 21)
Java SDK: /usr
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)

=== Xamarin.iOS ===

Version: 7.2.6.28 (Business Edition)
Hash: 606f31a
Branch: 
Build date: 2014-08-01 15:27:48-0400

=== Build Information ===

Release ID: 503000441
Git revision: befb6aa1176d37a5f678f4274f340a0159091b7a
Build date: 2014-09-08 17:57:02-04
Xamarin addins: 6dc7c388e31fdfc8014689839d37de0d4622435c

=== Operating System ===

Mac OS X 10.9.4
Darwin Hobbit-2.local 13.3.0 Darwin Kernel Version 13.3.0
    Tue Jun  3 21:27:35 PDT 2014
    root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
Comment 3 Chris Hardy [MSFT] 2017-06-27 19:33:10 UTC
Unfortunately, we’re unable to reproduce this report. If this issue is still occurring for you, please reopen this issue and attach a reproduction to the bug by starting with a clean Xamarin.Android project adding just the code necessary to demonstrate the issue.