httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randy Terbush <ra...@zyzzyva.com>
Subject Re: alloc.c etc.
Date Tue, 14 Jan 1997 14:39:45 GMT
> 
> Sameer (I think) wrote:
> >      How does this stuff work? I'm trying to track down a memory
> > leak...
> 
> rasmus@lerdorf.on.ca writes:
> > The only way something can leak is
> > if it gets into some sort of loop and keeps asking for more pools.
> > A second way something could leak is if it goes around the pool scheme and
> > does a malloc() on its own without free'ing the memory.  Perhaps a module
> > somewhere is calling strdup() or even malloc() directly in your code?
> 
> One other possibility is a memory leak in some other OS routine.
> For example, I know some (all?) versions of the regex stuff on
> linux leak.  Which I why I recommended using ours on Linux.
> 
> --
> Howard Fear      I'm just a country perl hacker Jim.        hsf@pageplus.com

I suspected this and switched over to using the HS regex we supply.
I'm still seeing the leak (manifested as swap growth). The swap is
immediately freed when the server is killed and restarted.

Looking at the HS regex stuff, it still looks as if there could be
some leakage there. Not clear.




Mime
View raw message