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.
This code in MonoAndroidFlavouredProject is deadlock prone:
> AsyncManager.Run (designerProject.DisposeAsync);
> catch (Exception e)
> tracer.Error(e, e.Message);
AsyncManager is not doing what we think. It is blocking the main loop, thus preventing tasks from being able to complete if they need to sync to the main thread for whatever reason. The result is a deadlock.
An example of the deadlock is: https://gist.github.com/alanmcgovern/77e16acf64ca7629332139296a804eb6
The stack trace is useful, but I'd appreciate some repro steps. It seems DisposeDesignerProject is being called right after a CreateProject, so I assume there's an active Android designer session and you're creating another new project while it's open? Does it matter what kind of new project it is?
Fixed in version 220.127.116.115 (cycle9)
Commit: f18ef199b768479ba936908ba82d24b9ade032b1 (xamarin/XamarinVS)
It would be great If you check this issue at your end. As per comment2 this issue does not exist any more.