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.
This is a serious bug and easily reproducible. Simply instantiate a class-level WebClient and fire off a DownloadDataAsync call to download a reasonably-sized file (say 5mb). When the DownloadDataCompleted event fires you can do whatever you like with the downloaded data, Dispose the WebClient if you wish, but a byte containing the data will remain in memory thereafter.
Used HeapShot to verify. You'll see byte in there, and if you turn on Inverse References you'll see System.Net.Sockets.Socket.SocketAsyncResult with very little Memory Size but with Root Mem equivalent to the file(s) just downloaded. Keep downloading files and the memory just keeps getting used up.
Looks like a duplicate of http://bugzilla.xamarin.com/show_bug.cgi?id=2619
This is related to bug #386, bug #2619 and bug #2620, and all of those have been fixed now.
The fixes will be included in MonoTouch 5.2.