Bug 2333 - Quitting MonoDevelop causes a crash
Summary: Quitting MonoDevelop causes a crash
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8.1
Hardware: Macintosh Mac OS
: High normal
Target Milestone: ---
Assignee: Mikayla Hutchinson [MSFT]
Depends on:
Reported: 2011-12-03 19:11 UTC by James Clancey
Modified: 2012-05-02 15:11 UTC (History)
3 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 James Clancey 2011-12-03 19:11:52 UTC
Quitting MonoDevelop through the Application Dock (or when the system is shutting down, or you're just logging out) mainly results in an error form to be sent to Apple. The error mostly occurs when you're running a project on iPhone Simulator, but sometimes it happens without it. See screencast at: http://screencast.com/t/68f1927D .The screencast also contains an exception which I don't know why occured but the exception's text is also shown on the video.MonoDevelop: 2.8.1Runtime: Mono 2.10.6 (tarball Fri Sep 16 00:13:06 EDT 2011)Operating System: Mac OSX (Unix Xamarin
Comment 1 Miguel de Icaza [MSFT] 2012-01-18 10:12:53 UTC
I get the same problem:

System.InvalidOperationException: Handle is not allocated
  at System.Runtime.InteropServices.GCHandle.get_Target () [0x00027] in /private/tmp/monobuild/build/BUILD/mono-2.10.8/mcs/class/corlib/System.Runtime.InteropServices/GCHandle.cs:81 
  at System.WeakReference.get_Target () [0x00000] in /private/tmp/monobuild/build/BUILD/mono-2.10.8/mcs/class/corlib/System/WeakReference.cs:95 
  at System.WeakReference.get_IsAlive () [0x00000] in /private/tmp/monobuild/build/BUILD/mono-2.10.8/mcs/class/corlib/System/WeakReference.cs:88 
  at GLib.ToggleRef.Toggle (Boolean is_last_ref) [0x00000] in <filename unknown>:0 
  at GLib.ToggleRef.RefToggled (IntPtr data, IntPtr handle, Boolean is_last_ref) [0x00000] in <filename unknown>:0
Comment 3 Mikayla Hutchinson [MSFT] 2012-01-18 13:25:22 UTC
I believe the BackgroundMonitor exception shown during the screencast was fixed several releases ago, and the crash cannot be debugged without a trace or reproduction steps.
Comment 4 Mikayla Hutchinson [MSFT] 2012-01-18 13:57:12 UTC
I can't reproduce this with the current version of MD by following the steps in the video. Do you still see this problem with current release of MD?
Comment 5 Attila Tamás Zimler 2012-02-05 15:46:08 UTC
As I'm also unable to reproduce the bug - may be fixed (will surely find out, if not because in most case I forget to shutdown MD before shutting down the system - and it is causing the same error if the problem exists). For now I would also vote for that the bug has been fixed.
Comment 6 Mikayla Hutchinson [MSFT] 2012-05-02 15:11:36 UTC
Okay, closing for now, we can reopen if it happens again.