[Jackit-devel] RE: [PlanetCCRMA] jack memory leak?

Nelson Posse Lago lago@that.com.br
Thu Nov 14 13:04:01 2002

On Thu, Nov 14 2002 at 08:00:13am -0800, Mark Knecht wrote:
>    Using the free -b command this morning I showed 375MB memory free in the
> line that start +/-.

I believe the best thing you can do is to try using the memstat program.
It takes a couple of seconds to run, but gives a very detailed report. For
this particular scenario, you need to watch two groups of data from it:

- take (just one of) the jackd PIDs and watch if the memory
  allocated to it changes significantly. This is the memory actually
  allocated to the process, excluding the text segment, shared libraries

- after the PIDs listing, there are a few "/SYSV000" entries; these are
  shared memory segments. For each one, there's a list of numbers that
  correspond to the PIDs of the processes that deal with it. Check the
  ones that list any of the jack PIDs. If they grow in size (very
  unlikely) or quantity (more plausible), you may have a leak.

There are quite a few programs that "grow" in memory as time passes up to
a certain amount (for example, bind); this is normal, and maybe one of
them is causing this behavior.

Hope this helps,