[Mono-list] Memory leak

Rodrigo Kumpera kumpera at gmail.com
Sun Feb 1 12:52:16 EST 2009


On Sun, Feb 1, 2009 at 1:57 PM, Jon Harrop <jon at ffconsultancy.com> wrote:

> On Sunday 01 February 2009 15:23:33 Rodrigo Kumpera wrote:
> > On Sun, Feb 1, 2009 at 1:22 AM, Jon Harrop <jon at ffconsultancy.com>
> wrote:
> > > I understand that Mono's new garbage collector has been delayed until
> > > Mono 2.9
> > > but someone else mentioned that even this new GC will still not be
> > > accurate and, therefore, is likely to leak memory indefinitely as well.
> > > Is that correct?
> >
> > Yes, toy programs designed to leak memory will still do with the new GC.
> In
> > practice a GC with conservative stack scanning has a larger working set
> dude
> > to floating garbage, but it's quite rare to cause pathological
> > leaks such as the one you crafted.
>
> Are you saying that larger programs that use this queue implementation will
> not leak?
>


This kind of leaks are usually caused by unused stack slots that retain the
dead value.
Regular code will overwrite those stack slots on method calls and let the GC
collect.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-list/attachments/20090201/3befc87c/attachment.html 


More information about the Mono-list mailing list