[Mono-devel-list] Garbage Collection problem

Paolo Molaro lupus at ximian.com
Mon Oct 6 10:00:31 EDT 2003

On 10/06/03 Jörg Rosenkranz wrote:
> > My uniformed guess is that we are not allocating the strings to be
> > collected for some reason, but this is totally uninformed
> > 
> > Miguel
> > 
> I have filed following bug for this behaviour:
> http://bugzilla.ximian.com/show_bug.cgi?id=49362
> I've tried the test case using byte arrays instead of strings which 
> causes the same results. So strings should not be the problem.

The test case didn't show any leak, so no leak should be expected by
changing the type of the allocated objects.
The only issue exposed was that GC.GetTotalMemory() returned the size of
the heap instead of the amount of memory allocated to objects: I fixed
this in cvs.
And, yes, the GC after a while will free also the heap memory, but
applications shouldn't expect it to happen at any particular time: it's
not their business to care about that:-)


lupus at debian.org                                     debian/rules
lupus at ximian.com                             Monkeys do it better

More information about the Mono-devel-list mailing list