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.
Although aapt task got parallel on last stable version it still does not work as expected (check loading of big project in Xamarin Studio and Visual Studio)
Please add option of manual AAPT synchronization - let this task do not run until build or manual click in button like "Synchronize resources".
AAPT still blocks UI thread and it is run too often! (compare with XS)
I'm seeing this too. I load up a project in VS2015 and everytime I click on Xamarin.Firebase.Common reference in the solutoin view aapt.exe spins up and uses 20% CPU and I can't do anything in the UI.
Created attachment 20469 [details]
I was able to replicate a similar behavior as described in Comment 0 locally yesterday in a small sample test case, and I was able to verify a candidate fix for that scenario. I have filed the details in Bug 53817.
I will tentatively mark this bug as a duplicate. If the original reporter of this bug (from Comment 0) still sees that "AAPT ... blocks UI thread and it is run too often" after updating to Xamarin.Build.Download 0.4.3-beta2 or higher, please do reply back with additional details about what might be different in your project compared to the test case on Bug 53817. If possible, please also collect a sample minidump or two from the busy instance of Visual Studio (similar to Bug 53817, Comment 1). You can then set the bug status to REOPENED. Thanks!
(If any other user who is not the original reporter from Comment 0 sees similar performance issues after updating the NuGet package, please file submit a new bug with the details. Thanks!)
*** This bug has been marked as a duplicate of bug 53817 ***