Bug 6582 - Unable to debug the app in the first go, as it gives the error Application has stopped unexpectedly. [Jelly Bean Device]
Summary: Unable to debug the app in the first go, as it gives the error Application ha...
Status: VERIFIED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.2.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-08-17 11:16 UTC by Nischal
Modified: 2013-03-14 08:15 UTC (History)
6 users (show)

Tags: papercut
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:
VERIFIED FIXED

Description Nischal 2012-08-17 11:16:46 UTC
Steps to reproduce:
1. Open any sample application.
2. Set the target framework as 4.0.3
3. Debug the application.
Actual result (a): Observe that the application does not launch successfully as it gives the error: Unexpectedly stopped working.

4. Now Run (Release) the application.
5. Observe that application Run successfully, with the non-blocking issue mentioned in the bug 6571
6. Now restart MD and again Debug the application.
7. The application debug successfully.

Expected result: The application should Run/Debug successfully in a first go, without throwing any error message.

Supplement information:
Device Logs: https://gist.github.com/3379007
MonoDevelop logs: https://gist.github.com/3379019
Android tools logs: https://gist.github.com/3379028

Environment information:
Windows 7
MD 3.0.4.4 - 22c5f7d7e622569de506bbdb89a1858418fdafc4
MFA 4.2.5.195540401 Alpha

Regression status: Regression as with the stable version a different issue is appearing when try to debug the application. Error: Failed to get package list. Data at the root level is invalid. Line 1 position 1.
Comment 1 Nischal 2012-08-17 11:17:55 UTC
Device information:
Nexus 4.1 JellyBean
Comment 2 PJ 2012-08-24 17:59:51 UTC
I am still unable to reproduce this bug.

Using:

MD 3.0.4.4 5eac10aa9d8a0ee2329b8ffe98f568b74dfd2f40

MFA 4.2.5 b2ad54e976e39bf9b0af4f652e21bec435303543

Here is the gist of my initial deploy on both a Galaxy Nexus and Nexus 7 (both Jellybean 4.1.1): https://gist.github.com/3455882



The one common factor (that doesn't show up on my ICS device deploys) is a large number of lines like this:
W/        ( 1302): Bad call to mono_mutex_lock result 11
F/        ( 1302): * Assertion at /Users/builder/data/lanes/monodroid-mac-monodroid-4.2.5-branch/b2ad54e9/source/mono/mono/metadata/loader.c:2146, condition `ret == 0' not met
W/        ( 1302): Bad call to mono_mutex_lock result 11
F/        ( 1302): * Assertion at /Users/builder/data/lanes/monodroid-mac-monodroid-4.2.5-branch/b2ad54e9/source/mono/mono/metadata/loader.c:2146, condition `ret == 0' not met
W/        ( 1302): Bad call to mono_mutex_lock result 11

Any more thoughts?

Nischal - can you still reproduce this?
Comment 3 Nischal 2012-08-27 02:52:31 UTC
Today, when we verified this with the latest version of the installers:

MD 3.0.4.4 - 5eac10aa9d8a0ee2329b8ffe98f568b74dfd2f40
MFA 4.2.5.235241842 - e058172371a9b09031a5d201496f9afff85820dc

This issue does not exists.
Comment 4 Kevin McMahon 2012-12-14 18:32:22 UTC
I get this repeatedly every time I recompile/redeploy fresh changes and then try to debug on Jellybean devices (Nexus 7 and Galaxy Nexus). Closing the app and restarting it works as does simply stopping the app and then trying to debug.

Version Info:
=============

MonoDevelop 3.0.5

Runtime:
	Mono 2.10.9 (tarball)
	GTK 2.24.10
	GTK# (2.12.0.0)
	Package version: 210090011
Apple Developer Tools:
	 Xcode 4.5.2 (1847)
	 Build 4G2008a
Mono for Android: 4.2.7
Android SDK: /Users/kevin/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.1   (API level 16)
Java SDK: /usr
Monotouch: 6.0.6 (Evaluation)
Build information:
	Release ID: 30005000
	Git revision: e159cf083bd327933166819d94245298898d6e3d
	Build date: 2012-10-24 16:43:06+0000
	Xamarin addins: eea2ed91ae8dd242b281d5ec8f6c2fbc63b4cd3d
Operating System:
	Mac OS X 10.8.2
	Darwin kmcmahon-mbp 12.2.0 Darwin Kernel Version 12.2.0
	    Sat Aug 25 00:48:52 PDT 2012
	    root:xnu-2050.18.24~1/RELEASE_X86_64 x86_64
Comment 5 narayanp 2013-02-21 06:18:56 UTC
Today, we have check this issue with latest builds:

gtk-sharp-2.12.20.msi
X.S 4.0 -a8219130080af6661ccd827d3ae2589bbfe8c2bb
mono-android-4.6.00049.msi

Device info:
Samsung Google Nexus (JellyBean 4.1)

This issue does not exist.
Comment 6 Jatin 2013-03-14 08:15:31 UTC
Today, with the latest builds:

MFA 4.6.01058 (Mac)
MFA 4.6.01055 (Windows)
Mono 2.10.12
XS 4.0.2.18

We have observed that this issue does not exists, as we are successfully able to debug the application on emulator/device.

Hence, closing this issue.