Re: [Audacity-devel] Nyquist memory leaks

[Adrian B. <ad...@gm...>]

Ok.  Sounds like the repetative ones aren't big enough to worry about.
 That's cool, I just thought it was odd that there wasn't any shutdown
function that would free all gc-owned memory and scratch space and
such.

As for OS cleanup, you should say all *useful* operating systems.=20
Many times I've lamented having to reboot windows 9x (often
involuntarily) while searching for memory leaks.  But thankfully, I
haven't had to do that in years.

Thanks for the info,
Adrian

On 9/14/05, Dominic Mazzoni <do...@au...> wrote:
> Adrian,
>=20
> Nyquist implements a full interpreted programming language, and in doing
> so it implements a lot of its own memory management, using garbage
> collection.  The first time Audacity calls Nyquist, it initializes it;
> after that, it never fully de-initializes everything, which makes things
> a little bit more efficient for future runs.  So many of Nyquist's
> internal data structures are never freed (until, as you note, the whole
> process exits).  But they shouldn't grow without bound - it's just that
> some data structures are not automatically cleaned up every time.
>=20
> Trust me, before I fixed the "real" memory leaks, calling Nyquist would
> leak several megs per call.  If there are any leaks left, they're pretty
> tiny in comparison.
>=20
> By the way, it's not just XP that will clean up all used memory when a
> process exits - this happens on all operating systems.  The only
> exceptions are things like GDI resources on Windows - but Nyquist
> doesn't use any of these.
>=20
> - Dominic
>=20
>=20
> Adrian Bentley wrote:
> > While futzing around with the source code, I've noticed that nyquist
> > effects have memory leaks (e.g. "High Pass Filter..." seems to leak 4k
> > per run).  I saw some earlier conversations about this, but there
> > didn't seem to be any sort of conclusive result.
> >
> > There are only a few largish unreleased chunks, which are all one time
> > Nyquist init time allocations (stack space, arg space, etc.).  There
> > appear to be a lot of small leaks (which makes sense if their from the
> > lisp code), some of which look like they're coming from the one time
> > initial setup for xlisp as well.  From what I can tell xlisp does NO
> > cleanup of this initial memory in any function that looks like an exit
> > function (I don't know for sure about dynamic/gc-owned memory).
> >
> > It doesn't seem to be a HUGE deal since I will never be running
> > effects that many times and I'm working on XP which will cleanup
> > everything when the process exits.  I was just wondering if there was
> > a plan of attack for this stuff at all?
> >
> > Thanks,
> > Adrian
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by:
> > Tame your development challenges with Apache's Geronimo App Server.
> > Download it for free - -and be entered to win a 42" plasma tv or your v=
ery
> > own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.p=
hp
> > _______________________________________________
> > Audacity-devel mailing list
> > Aud...@li...
> > https://lists.sourceforge.net/lists/listinfo/audacity-devel
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server.
> Download it for free - -and be entered to win a 42" plasma tv or your ver=
y
> own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Audacity-devel mailing list
> Aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>