Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Steps to reproduce:
1.Install MonoDevelop 2.8.6.
2.Open MonoDevelop from application.
3.Click File>New or click Create Solution
MonoDevelop crashed on Mac(10.7) and user unable to open/create solution.
MonoDevelop should not be crashed and solution should be open and create.
Mono for Android 4.0.2
Please click below URL to see video of this bug.
Created attachment 1139 [details]
Stacktrace for crash
Bug is not present on Windows versions (tested Windows 7)
Reproduced on MAC 10.7.2 (Lion)
Stack trace in attachment
What version of Mono are you using?
(I know I answered you on IRC, but putting it out in public record.)
I cannot reproduce the issue. I have the same mono, mono for android, monotouch and MonoDevelop. Is there anything else that might be relevant to this?
I am now unable to reproduce.
I got the error this morning 3 times in a row. Then I updated my mono framework from the site to 188.8.131.52 after you couldn't reproduce to test.
Since then I have not had the crash.
I have now uninstalled MonoDevelop and Mono, reinstalled and re-updated. At each point, I was able to open solutions and files and create new solutions and files.
I will be in touch with 360 and see if they can reproduce and distill a test case.
What is the Mono version that you are using?
Can you go to MonoDevelop/About box and get the version number for Mono?
is it 184.108.40.206 or 2.10.8?
The difference is that the .1 contains the new Gtk+ stack, the 2.10.8 has the old stack.
I tested as extensively as I could with both 2.10.8 and 220.127.116.11. I was unable to reproduce any issue.
I just ran into this issue after installing 2.8.6 but cannot get it to re-occur,
Action: Click New-> Solution
Mono 2.10.8 (tarball Mon Dec 19 17:43:18 EST 2011)
Attached Crash Report: MD286Crash.txt
Created attachment 1144 [details]
Crash Report from MonoDevelop 2.8.6
Alan, we used Mono Framework 2.10.8 on Mac 10.7(Lion).
Steps to reproduce:
2.Two window appears (MonoDevelop application window and Welcome MonoDevelop window)
3.Don't close both window
4.Create solution using MonoDevelop application
5.Solution created and Mono develop application working fine.
6.Close 'Welcome MonoDevelop window'.
7.Create solution using MonoDevelop application.
Please click below link to view this issue.
I am now able to reproduce. Thanks Saurabh!
The 'Welcome MonoDevelop' screen referenced is a pop up that can be disabled for future starts via checkbox.
To clear this setting, look to ~/Library/Preferences/Monodevelop-2.8/MonoDevelopProperties.XML
On the second to last line (or FIND) look for <Property key="Xamarin.Ide.Welcome.Mac.ShowNextTime" value="False" />.
Change to "True" to re-enable the welcome screen and reproduce the bug as shown.
That explains why I couldn't repro it. Looking into this now, I also pinged marek as he may have some ideas on this as he wrote the welcome window.
The issue was caused by the new welcome window code. This is not supposed to be enabled for the foreseeable future so I simply disabled this and backported the fix to the 2.8.6 branch. We need to rebuild mono 2.8.6 from the branch so that commit 'd0116e1a2cd' is used.
The bug in question has already been found and fixed so once 2.8.6 is rebuilt with commit d0116e1a2cd the bug can be closed.
Closing as this is fixed. MonoDevelop 2.8.6 needs to be rebuilt to test the fix though.