SWIG Python - memory growing out of bounds

On 20 Jan 2006 12:34:41 +0100, Lars Gullik Bjønnes
<larsbjgullik.net> wrote:
> | On Fri, 2006-01-20 at 02:25 +0100, Lars Gullik
Bjønnes wrote:
> | > Hi,
> | >
> | > I have tried to setup trac for use with
subversion (1.3.0). So far
> | > with little success. During the initialization
of the database, it
> | > crashes due to excessive use of memory. I have
used som time on this
> | > and have tracked this problem down to a problem
with the pools and
> | > svn_swig_py_make_editor. I have now reached the
point where I am
> | > unable to make further progress.
> | >
> | > Please have a look at the trac ticket I entered:
> | > http://
projects.edgewall.com/trac/ticket/2620
> | >
> | > If I can get some directions on how to proceed
and what to test now
> | > I'd be happy.
>
> That is where I am comming from (or the ticket system
really) ... as
> said: "problem with the pools and
svn_swig_py_make_editor", which is
> from the libsvn python bindings.

Hi Lars,

Thanks for your bug report! This bug has been fixed in
Subversion
trunk and the fix should be included with 1.3.1. If you
would like to
fix your local copy, please see the patch included in the
Trac issue:
http://
projects.edgewall.com/trac/ticket/2620

Sorry for the delayed response! In future, please send bug
reports to
<devsubversion.tigris.org>. If the bug is regarding
the Python
bindings you can cc me to bring it to my attention.

Cheers,

David


--
David James -- http://www.cs.toront
o.edu/~james

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesubversion.tigris.org
For additional commands, e-mail: dev-helpsubversion.tigris.org