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.
I have a slightly oddball config.
I'm using Mono 2.10.7 (came with MD2.9), but with MD 2.8.5
If I do a quick build -> fix something -> build - fix something cycle, after 2 or 3 'rounds' (ie, about 30 seconds), the process beach balls.
I can force quit MD, and it's removed from the task manager, however the window doesn't go away, and I can't kill the mono process either. Reboot is the only option.
I assuming it's a 2.10.7 problem. Can I force 2.10.6 (or just reinstall it?). Is there any way to get a debug log out of it? Being I can't kill it (Activity Monitor or kill -9), I doubt it, but worth asking.
The unkillable process is a Mono bug, see bug 2548. You'll have to kill the matching gdb process.
The native crash that triggered it is probably GTK+.
The workaround for the unkillable process is to set the env var MONO_DEBUG=no-gdb-backtrace but I expect you'd still get a crash. If you could attach the crash report from the Apple crash reporter that'd be useful.
Newer versions of mono have fixed the issue where a native crash would cause gdb to hang, so this can be closed
Please close it. I've not had this problem in _ages_.