Bug 45018 - Possible memory leak of whole Task chain for SDK resolving
Summary: Possible memory leak of whole Task chain for SDK resolving
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: unspecified
Hardware: PC Mac OS
: High major
Target Milestone: master
Assignee: dean.ellis
Depends on:
Reported: 2016-10-04 16:47 UTC by Marius Ungureanu
Modified: 2017-03-31 14:21 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Comment 1 Marius Ungureanu 2016-10-04 19:47:53 UTC
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.
Comment 2 dean.ellis 2016-10-05 14:22:54 UTC
PR up https://github.com/xamarin/xamarin-android/pull/251
Comment 3 dean.ellis 2017-03-31 14:21:27 UTC
fixed in Xamarin-android/master/a28c7269