This is Xamarin's bug tracking system. For product support, please use the support links listed in your Xamarin Account.
Bug 9572 - Bad call to mono_mutex_lock result 11
Summary: Bad call to mono_mutex_lock result 11
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler (show other bugs)
Version: 4.4.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-01-15 11:22 UTC by jonathan_chapman
Modified: 2013-03-14 10:52 UTC (History)
4 users (show)

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


Attachments

Description jonathan_chapman 2013-01-15 11:22:22 UTC
In 4.4.54 I performed the following steps on a Samsung Nexus with 4.1.

1. Run application
2. Killed application through the running applications.
3. Cleaned data through settings/Apps
4. Tried to run the application again.

and got an infinite number of the following before I killed the application again.

01-15 11:15:46.864 W/        (13184): Bad call to mono_mutex_lock result 11
01-15 11:15:46.864 F/        (13184): * Assertion at /Users/builder/data/lanes/monodroid-mac-monodroid-4.4-series/c6e52015/source/mono/mono/metadata/loader.c:2181, condition `ret == 0' not met

and the application would not start.
Comment 1 Sebastian Krysmanski 2013-02-06 03:00:41 UTC
Yes, I'm having exactly the same issue. I'm running a Galaxy Nexus with Android 4.2.1.

As temporary workaround you can disable "Use Fast Deploy" in the project settings to make the deployment work again properly.
Comment 2 Jeremy Kolb 2013-02-28 16:24:41 UTC
I'm seeing this as well with a Galaxy S3.
Comment 3 Sebastian Krysmanski 2013-03-01 09:32:39 UTC
This still happens with MfA 4.6.
Comment 4 Jonathan Pryor 2013-03-14 10:52:22 UTC
Fixed in monodroid/47387e9e.

Note You need to log in before you can comment on or make changes to this bug.