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 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.
When I open an existing project in VS2010, and then cancel the resultant Updater window, the UI locks up for about 10s.
360logica cannot seem to reproduce this at all. PeterC can reproduce it 2/5ths of the time. I can reproduce it reliably, although I do sometimes see that it works as expected. Perhaps there's a race involved.
It's worth noting that Dean and Dominique each say they can't reproduce.
Steps to reproduce:
1) Create an android project
2) Close VS
3) Open VS
4) Select the created project from the list of recent solutions in the welcome page
5) Project loads, Updater dialog appears
6) Cancel the Updater dialog
7) Immediately try to edit the text in the .cs file or select files in the solution explorer
This should work every time
Depending on who is reproducing, some % of the time the UI will freeze up, getting to the point of windows saying the program is Not Responding. This is indicated by the whitening of the entire window and the title bar changing to say (Not Responding).
I attached a VS2012 instance to VS2010, and tried to get the call stack while VS2010 was paused, here's what I got on a few attempts: https://gist.github.com/pjbeaman/e873adf6635f3a0c4743 (doesn't seem tremendously helpful, but perhaps you guys will know!)
Here's a screencast of the behavior: http://www.screencast.com/t/8CUSFBS23
Win7x64 (PeterC reproduced on Win8x64 as well)
VS2010 (nobody has reproduced on VS2012)
not reproducible in VS 2012 or newer. VS 2010 no longer supported for XMA.