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 3155 [details]
Trace obtained through gdb
Clicked 'Quit' in the MonoDevelop menu, then it hung up, causing one CPU core to go up to 100%.
In the attachment you can find a gdb trace. I did also the steps described in 'Reporting Bugs' --> 'Managed Hangs', but there are no instructions about how to obtain the log files.
The log files are in ~/Library/Logs/MonoDevelop-3.0
From the native trace it looks like the MD's main thread has finished and the runtime is waiting for threads to shutdown. Unfortunately all the threads are also waiting for various things - signals, reads, etc. It could be that one of the threads needs to be marked as a background thread so it doesn't prevent shutdown, or it might be a runtime bug.
Maybe a dup of bug 5647 or bug 7003.
Thanks so much for taking the time to submit this report! I attempted to reproduce this issue based on the bug description with the latest Visual Studio 2017 for Mac Preview version 7.2, and I was unable to hit the problem. If this issue is still occurring for you, please reopen this report and attach a reproduction, ideally starting with a new template project and then adding just the code necessary to demonstrate the issue.