Bug 5864 - NUnit crashing at MonoDevelop start.
Summary: NUnit crashing at MonoDevelop start.
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 3.0.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-06-26 09:55 UTC by hellagolyonis
Modified: 2013-12-05 18:35 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:

Comment 2 Mike Krüger 2012-06-27 08:10:47 UTC
Seems to be a race in the addin loading.
Comment 3 Alan McGovern 2012-09-17 13:10:45 UTC
Can you still reproduce this issue? If so, can you attach a copy of the MonoDevelop.log file from a session where MonoDevelop has crashed. The log can be found in:

C:\Users\<USER NAME>\AppData\Local\MonoDevelop-3.0\Logs

Just replace 'user name' with the name of your user account. Also the 'AppData' directory is hidden by default so you may not see it in Explorer if you have not enabled showing hidden/system files in the Explorer options.
Comment 6 PJ 2013-11-19 17:05:05 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 7 PJ 2013-12-05 18:35:28 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.