Um ...
so say I have a mod perl thing (template wotsit and lots of
class::methodmaker stuff) and I notice everytime I serve a page the size
of the apache client increases slighlty ...
I know a memory leak when I see one and I', looking at one right now
so what is the preffered debu
Robin Szemeti sent the following bits through the ether:
> so what is the preffered debugging method for discovering what this
> little leak might be .. strip the app down and build bit by bit .. or is
> there a clever way of looking at heap contents?
The mod_perl guide is your friend:
http://pe
From: "Robin Szemeti" <[EMAIL PROTECTED]>
> so what is the preffered debugging method for discovering what this
> little leak might be .. strip the app down and build bit by bit .. or is
> there a clever way of looking at heap contents?
Would MJD's Memoize (http://search.cpan.org/search?dist=Mem
On Thu, 10 May 2001, you wrote:
> From: "Robin Szemeti" <[EMAIL PROTECTED]>
>
> > so what is the preffered debugging method for discovering what this
> > little leak might be .. strip the app down and build bit by bit .. or is
> > there a clever way of looking at heap contents?
>
> Would MJD's M
On Thu, 10 May 2001, you wrote:
> Robin Szemeti sent the following bits through the ether:
>
> > so what is the preffered debugging method for discovering what this
> > little leak might be .. strip the app down and build bit by bit .. or is
> > there a clever way of looking at heap contents?
>
Robin Szemeti:
> chances are it isnt a leak at all, just cached info filling up the planet
> .. more investigation needed.
If it turns out that the caching is good but unpredictable in terms of
how much caching will occur have a look at Apache::SizeLimit
Hans.
