[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Source of memory leak in mod_proxy?

From: Justin Erenkrantz <jerenkrantz_at_apache.org>
Date: 2002-09-05 02:24:07 CEST

On Wed, Sep 04, 2002 at 05:17:29PM -0700, Greg Stein wrote:
> Yup. On the error exits, too.

Hmm. On the error exits, shouldn't the request pool get cleaned up
right after that? But, for the successful cases, it makes sense to

> You know... I bet this will also solve the 'svn import' problem that we've
> been seeing lately. In that case, the server memory just skyrockets,
> proportional to the amount of data imported. This would do it.

Hmm. Why wouldn't they be cleaned up when the request pool
is cleaned up? I wonder if its something else there. As,
svn import is multiple-request based rather than one large
commit, right? So, r->pool would be cleaned up on each request
and the brigade freed.

Or, maybe I'm missing something... -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 5 02:24:42 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.