Bug 9171 - MonoDevelop crashed again...
Summary: MonoDevelop crashed again...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 3.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
: 9170 ()
Depends on:
Reported: 2012-12-31 09:58 UTC by Jonas Sourlier
Modified: 2013-12-05 18:36 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

crash dump (744.02 KB, text/plain)
2012-12-31 09:58 UTC, Jonas Sourlier

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 Jonas Sourlier 2012-12-31 09:58:57 UTC
Created attachment 3150 [details]
crash dump

When debugging on my iPod touch, MonoDevelop just said "Could not connect to debugger" (again) and hung up, with CPU going to 100%.

Please fix this, it's so annoying.
Comment 1 Jonas Sourlier 2012-12-31 09:59:48 UTC
*** Bug 9170 has been marked as a duplicate of this bug. ***
Comment 2 Alan McGovern 2013-01-02 09:07:47 UTC
How did you generate that crash dump? It does not indicate that MonoDevelop has crashed and it seems to contain a stacktrace for every single running application on your system. Usually when an application crashes on MacOS, a dialog will be displayed containing the stacktrace for the application that has crashed. Would you be able to attach the contents of that dialog if it happens again? 

Alternatively, can you create a screencast demonstrating the problem using something like Jing ( http://www.techsmith.com/jing.html )?
Comment 3 Jonas Sourlier 2013-01-02 14:08:37 UTC
The crash dump was the one that my Mac tried to send to Apple. In the future, I'm going to attach the crash dump the way you suggested.
Comment 4 Mikayla Hutchinson [MSFT] 2013-01-03 07:27:40 UTC
This looks like an Apple hang trace, not a crash trace. This is what MacOS reports to Apple when an app stops responding. Unfortunately it doesn't contain very useful stack frames for Mono apps.

If this happens again, could please you obtain a Mono hang trace?

Comment 5 Jeffrey Stedfast 2013-08-05 13:09:11 UTC
does this still happen?

If it does, could please you obtain a Mono hang trace?

Comment 6 PJ 2013-11-19 17:05:50 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:36:18 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.