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

Memory leak remains in 1.6.3?

From: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 24 Jun 2009 10:03:44 -0400

I have not yet tested this with the command-line client. I hope to
today, but other priorities may get in the way.

One of my users is reporting problems locking a bunch of files on one
of his workstations, so I've been trying to reproduce the issue. I
asked him to upgrade to 1.6.3 and he's still testing. I upgraded
myself to 1.6.3 this morning, and while I can't reproduce his issues
(couldn't with 1.6.2 either), I'm observing a large amount of memory
used and not released.

Steps to reproduce:
1) I have a WC of 848 PDF files, total size about 1GB (excluding .svn
2) Select all PDFs, right-click, TSVn _> Get Lock
3) Lock Files dialog takes a while to populate, but it's 848 files - I
kind of expect that
4) Make sure all all are selected and click OK
5) All files are successfully locked. TortoiseProc.exe shows a Virtual
Size of 649MB, Working Set of 440MB in Sysinternals Process Explorer
(I have 2GB physical RAM)
6) Click OK. TortoiseProc.exe does NOT disappear from Process Explorer
(I gave it over a minute). Rest of system is bogged down heavily due
to this memory usage.
7) Terminate TortoiseProc.exe and system behavior returns to normal.

The exact same thing happens when I follow this sequence in unlocking
the files as well.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-06-24 16:03:57 CEST

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

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