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.
Created attachment 3150 [details]
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.
*** Bug 9170 has been marked as a duplicate of this bug. ***
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 )?
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.
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?
does this still happen?
If it does, could please you obtain a Mono hang trace?
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.
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.