memory usage in mod_perl

Max Kanat-Alexander mkanat at
Wed Jan 17 00:56:33 UTC 2007

On Tue, 16 Jan 2007 19:53:19 -0500 David Miller <justdave at>
> I was guessing that's probably what it was.  We don't have a whole
> lot of variables that are likely to occupy huge amounts of memory.  A 
> buglist is a darn good candidate.  A good start would probably be 
> undef'ing the bug object cache in our cleanup handler.
	Yeah, that is a good idea, and I'd love to do it. The problem is
that we can't get that variable anymore--it's actually been undefined by
perl, but perl didn't release the memory.

	Basically what I'd really love to do is force perl to release
all unallocated memory, but I have *no* idea how to go about that.

Competent, Friendly Bugzilla Services. And Everything Else, too.

More information about the developers mailing list