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

Why so many open connections?

From: Michael Pruemm <mpruemm_at_gmail.com>
Date: Thu, 11 Jul 2013 14:31:40 +0000 (UTC)

I'm trying to learn to use the svn api via the Python swig bindings
for 1.8.0. So I wrote some naive code that calls svn_client_log5 and
in the callback does something like this:

    foreach file in changed_paths:

The pool passed to svn_client_ls3 is the one passed to the callback

(I first tried to use svn_client_list3 but the Python bindings lack
(support for its callback function.)

This works fine for a while when I access the repository via http://
but eventually lots of connections are open and the script just hangs
and doesn't even react to ^C.

When I access the repository via svn+ssh:// it works fine until I
reach a commit that touched more than ~512 files. At that point, svn
is unable to open more connections to the repository, and a process
listing shows that there are 512 active processes connecting with the

Apparently, these connections are only closed when the memory pool is
cleared/destroyed but this behaviour is not documented anywhere. Is
this a bug?

- Michael
Received on 2013-07-11 16:32:54 CEST

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

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