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

Re: Apache memory leak with TSVN 1.5.x clients

From: Stefan Fuhrmann <stefanfuhrmann_at_alice-dsl.de>
Date: Mon, 13 Oct 2008 17:22:35 +0200

Patrick Bureau <pbureau_at_gmail.com> wrote on 10 Oct 2008 14:52:22 -0400
 
> We tried the new experimental build on two computers.
> The problem is unfortunately still there.

Well, there are no other differences between SVN CL
and TSVN I am aware of. What remains is the slightly
different usage of the SVN API that Stefan Küng already
described in his initial reply.

> I'm wondering what else could be different between TSVN 1.4 and 1.5...
> Is there anything we could do to help in tracking the problem down?
> (Install, trace, test, etc)

There is one feature that might tweak the internal
command order: switch the protocol engine from
NEON to serf. The latter will allow for multiple,
interleaved request to be sent by the client. Maybe
that makes the CL client fail as well or reduces
the issues with TSVN.

From http://svn.collab.net/repos/svn/trunk/subversion/libsvn_ra_serf/README:

> As Neon is currently Subversion's default RA DAV layer, you also need
> to add "http-library = serf" to your ~/.subversion/servers file to
> choose ra_serf at runtime.

Furthermore, do you use HTTP compression or
something similar that might explain why some
data is kept longer than usual?

-- Stefan^2.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-10-13 17:21:36 CEST

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

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