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

Re: Memory leak remains in 1.6.3?

From: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 24 Jun 2009 11:42:32 -0400

On Wed, Jun 24, 2009 at 11:28, Todd C. Gleason<tgleason_at_impac.com> wrote:
>> -----Original Message-----
>> From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
>> Sent: Wednesday, June 24, 2009 9:19 AM
>> To: users_at_tortoisesvn.tigris.org
>> Subject: Re: Memory leak remains in 1.6.3?
> ...
>> Locking/unlocking is usually done on very few files, so the svn library
>> is optimized for that. Locking/unlocking hundreds of files indicates not
>> a problem with svn but with your workflow (seriously: are you *really*
>> working on all those 848 files at once?).
> I think it's a valid use case.  Consider that I may have a large search-replace or other refactoring operation to run, and before I do it, I want to lock all affected files.  They may be binaries if I'm using a binary-capable editing or search/replace tool.

Valid, but rare use case I think.

The behavior I'm seeing is definitely preferable to what the other
user here experienced with 1.6.2 - Explorer crashed entirely,
necessitating a reboot of the system to get back to normal.

We have a feeling that AV (Symantec Corporate) is somehow involved,
but I can't say for certain yet.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-06-24 17:43:30 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.