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

Re: python bindings leak memory (Re: 1.7.0-beta1 up for testing)

From: rupert.thurner <rupert.thurner_at_gmail.com>
Date: Sun, 17 Jul 2011 20:00:10 -0700 (PDT)

On Jul 17, 10:16 pm, Philip Martin <philip.mar..._at_wandisco.com> wrote:
> "rupert.thurner" <rupert.thur..._at_gmail.com> writes:
> > now it works ... and running it for 100'000 revisions slowly increases
> > #!/usr/bin/python
>
> > import svn.client
> > import svn.core
> > import svn.ra
>
> > pool = svn.core.Pool()
> > client = svn.client.create_context(pool)
> > client.config = svn.core.svn_config_get_config(None)
> > client.auth_baton =
> > svn.core.svn_auth_open([svn.client.get_simple_provider(pool)], pool)
>
> > ra = svn.client.open_ra_session("http://gcc.gnu.org/svn/gcc", client,
> > pool)
> > def rcvr(orig_paths, rev, author, date, message, pool):
> >     if orig_paths is not None:
> >         for x in orig_paths:
> >             orig_paths[x]._parent_pool.destroy()
>
> Destroying pools like that was a workaround for a bug that has been
> fixed.  It's only safe if nothing uses, or explictily destroys, the
> pool.

how are the pools correctly destroyed? i tried to use the subversion
test cases to find a small example for replay, but it seems to be not
tested at all? is there some documentation you could point to which
shows how to use replay correctly?

rupert
Received on 2011-07-18 05:00:53 CEST

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