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.
Whilst trying to replicate a different bug I created a new solution in XS (iOS, Phone, Single View Application).
After adding a simple static class with a static DoSomething() method that does nothing I could no longer put any breakpoints. Trying to compile resulted in a spinning beachball and I had to kill XS. Restarting XS and it behaves correctly.
next time you get one of those spinning beachballs, could you open a terminal and use `ps ax | grep -i xamarin` to get the pid of Xamarin Studio and then run `kill -QUIT <pid>`?
This will force the Xamarin Studio to dump a stacktrace of each thread into ~/Library/Logs/XamarinStudio-4.0/Ide.log so we can see what is going on (probably a deadlock or a really slow section of code)
might have been related to a deadlock issue when adding breakpoints that I recently discovered/fixed