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
GitHub or Developer Community 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 7022 [details]
Description of Problem:
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Steps to reproduce the problem:
1. Scroll thru warning messages after compilation
XS should not crash
How often does this happen?
I can't reproduce this, we may have to see if a developer can figure out what's going on from the stack trace. If you have a chance, it might also be helpful to include some other pieces of information.
Could you please provide a test case to reproduce this issue at our end ?
Hello, can you still reproduce with latest version of Mono? If that's the case, please reopen the bug and provide a repo case. Thank you.