Bug 2714 - MonoDevelop crashes as soon as I click on the compile icon
Summary: MonoDevelop crashes as soon as I click on the compile icon
Status: RESOLVED DUPLICATE of bug 2605
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-01-02 16:45 UTC by Joe Wilcox
Modified: 2012-04-04 22:28 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 Joe Wilcox 2012-01-02 16:45:28 UTC
With random frequency, when I click on compile, MonoDevelop crashes.  It gives no output and the log has nothing of use.  Let me know if you really need it attached.  The only thing I can think of is that my Application Output window is detached and is floating.
Comment 1 Sebastien Pouliot 2012-01-03 05:33:17 UTC
can you give us the version number of MonoDevelop ?
Comment 2 Joe Wilcox 2012-01-03 23:00:57 UTC
I updated the to show 2.8 but it's really 2.8.5.  There just isn't a 2.8.5 option in the dropdown.
Comment 3 Mikayla Hutchinson [MSFT] 2012-04-04 22:28:38 UTC

*** This bug has been marked as a duplicate of bug 2605 ***