On 27.05.2010 08:42, Lieven Govaerts wrote:
Hi,
On Mon, May 24, 2010 at 3:51 PM, Lieven Govaerts<svn...@mobsol.be> wrote:
On Sun, May 16, 2010 at 10:38 AM, Stefan Küng<tortoise...@gmail.com> wrote:
Hi,
During the last few days, I've changed TSVN to link against the svn trunk.
The speed is much better now, so thanks for that. It's not as fast as the
1.6.x branch yet but it's usable.
About my problem:
serf is now the default DAV lib svn uses. But with serf I get tons of app
crashes (serf calls abort() - something I won't discuss here anymore since
you all should know my opinion about that).
For example: a simple checkout of the svn trunk crashed after about 5
seconds. Subsequent updates did too - I had to run cleanup and restart the
update 27 (!!) times until I had the svn trunk on my harddrive.
I'm using serf 0.6.1, but the same problem existed with 0.3.1. I updated to
0.6.1 yesterday hoping it would solve the problem, but apparently didn't.
I have prepared serf 0.6.2 with this fix at:
http://serf.googlecode.com/svn/branches/0.6.x
Can anyone of you reporting this problems test if this makes them go away?
Tested with a fresh build of TSVN. The crashes are gone now, at least I
didn't get one during my tests.
Checkout takes plenty of memory with ra_serf, way more than when using
ra_neon. I suspect these changes didn't make that worse, rather the
choice of pools for file-related requests in ra_serf (not the serf
library). I'll look into this.
Yes, there's a massive memory leak somewhere. A checkout of the TSVN
trunk used up more than 2GB or RAM.
I had to stop a test checkout of the KDE trunk once it used up more than
3.5 GB and basically slowed down my whole system.
To compare, I switched to neon and the memory use didn't grow over about
60MB.
All this tested on Win7 x64.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
