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.
Might have to unregister the loggers set, as the initialization will register the delegates which keep the task alive on a static event handler:
This only causes the memory held by all the tasks alive for the duration of the build process, which can skyrocket (260MB is allocated just for reading the assemblies via DirectoryAssemblyResolver.ReadAssembly)
For some reason, this isn't cleared up under Mono with xbuild/msbuild. MSBuild on CLR definitely frees up this memory.
PR up https://github.com/xamarin/xamarin-android/pull/251
fixed in Xamarin-android/master/a28c7269