Bug 5793 - Both MonoDevelop and VS2010 with MonoDroid 4.2.3 locks the mdb database on crash or stop debug
Summary: Both MonoDevelop and VS2010 with MonoDroid 4.2.3 locks the mdb database on cr...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 3.0.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-06-21 01:54 UTC by Juro
Modified: 2012-06-25 10:26 UTC (History)
2 users (show)

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:

Description Juro 2012-06-21 01:54:01 UTC
This also happened with 4.2.2 and it still happens with 4.2.3.
If debugger is stopped (due to a crash or on-demand) while the code is running in dependent assembly (class library), it locks its .mdb program database what blocks any further deploying and breaks the Intellisense. I can see that devenv.exe is keeping the mdb file handle opened.
I must close/reopen the VS (or MonoDevelop) each time it happens.

My config:
Windows 7 x64
VS 2010 ultimate
MonoDevelop for Windows
Mono for Android 4.2.3
Comment 1 Jeffrey Stedfast 2012-06-21 11:32:44 UTC
This isn't/wasn't a bug in Mono4Android, it is/was a bug in MonoDevelop.

I thought I had fixed this, but jpobst recently found/fixed the code to properly dispose the mdb files.

Unfortunately this commit didn't seem to make it into