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 for Bug 11098 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
The following code causes memory to leak forever until the program eventually crashes:
static void Main(string args)
var cache = HttpRuntime.Cache;
//Keep inserting new arrays into the cache with the same key
cache.Insert("key", new byte, null, Cache.NoAbsoluteExpiration, TimeSpan.FromSeconds(1));
Console.WriteLine("Used memory = " + GC.GetTotalMemory(true));
This happens because when you insert into the cache, it never releases its reference to the previous object you're replacing. The bug can be worked-around by calling Remove("key") before inserting.
I verified it leaks in mono 220.127.116.11, but I'm pretty sure it leaks in trunk too. It doesn't leak on Microsoft's implementation of Cache. The issue does not have anything to do with what garbage collector is used -- the caching code seems to keep references to the objects.
I found this when porting an asp.net application to mod_mono. This application frequently updated cache items with new objects, and as a result, this bug caused mono to leak away all 4gb of the server's memory after just a couple hours.