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

Re: SVN::Client -- why does this leak?

From: Nik Clayton <nik_at_ngo.org.uk>
Date: 2006-11-10 19:33:33 CET

Ben Collins-Sussman wrote:
> On 11/10/06, Malcolm Rowe <malcolm-svn-dev@farside.org.uk> wrote:
>> On Fri, Nov 10, 2006 at 08:27:41AM +0000, Nik Clayton wrote:
>> > Ah. So if I have a pool, create an object of type A in it, delete that
>> > object, and then create a second object of type A in the pool, the pool
>> > won't reuse the memory allocated for the first object, and will instead
>> > grow in size?
>> There's no concept of 'deleting an object' within APR's memory pool
>> scheme, only of clearing/destroying a pool, so yes.
> In other words, in a pool-based memory paradigm, the only three
> concepts which exist are:
> * allocate an object in some pool
> * create a subpool of a pool
> * clear/destroy a pool

Thanks for all the comments chaps, that makes things a fair bit clearer.

In gratitude, I offer up:


It behaves a little differently to ViewVC, because I don't like the way
ViewVC does things. If those things annoy you too you'll probably like
that. Of course, if you don't, they won't.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 10 19:33:55 2006

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