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 7455 [details]
call stacks 1
This happens a lot recently (not sure whether it's due to Xamarin SDK updates.)
Often time when I hit an unhandled exception in my android app (running on a real phone), I click on the Continue button in order to see more information in the Debug output window. However Visual Studio lost response. Trying to operate on VS will make a tooltip appear near the toolbar tray saying "Microsoft Visual Studio is Busy...".
I have two dump files, they have slightly different call stack on the VS Main thread though. Not sure how to submit the dumps because they are around 1 GB each.
Created attachment 7456 [details]
call stack 2
I have checked this issue with unhandled exception and hit to continue.
I observed that Visual Studio is not deadlocks after continue on an exception
Please check the screencast and let me know if I missed any steps here.
Microsoft Visual Studio Professional 2013
Version 12.0.30501.00 Update 2
Microsoft .NET Framework
Xamarin 18.104.22.168 (48bc8a484441700b633a09133e208654bf62fa12)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android
Unfortunately, we’re unable to reproduce this report. If this issue is still occurring for you, please reopen this issue and attach a reproduction to the bug by starting with a clean Xamarin.Android project adding just the code necessary to demonstrate the issue.