[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: Todd C. Gleason <tgleason_at_impac.com>
Date: Wed, 24 Jun 2009 09:32:38 -0700

> -----Original Message-----
> From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
> Sent: Wednesday, June 24, 2009 10:19 AM
> To: users_at_tortoisesvn.tigris.org
> Subject: Re: Memory leak remains in 1.6.3?
> Andy Levy wrote:
> >> But anyway: the memory consumption is inside the svn library
> >> so you should report this to the svn mailing list.
> >>
> >> Just try
> >> $ svn lock --targets path/to/textfile/containingAllPathsToLock
> >>
> >> and check the memory use of the CL client.
> >
> > Confirmed with 1.6.2 (haven't upgraded to 1.6.3 yet), BUT there is a
> > major difference here - when the CL client finishes the locks, it
> > releases the memory and terminates within 2 seconds. When I use TSVN,
> > TortoiseProc.exe remains in the process list after I close the window
> > and the memory is not released.
> That's because the CLI is single threaded (it has only one thread) and
> therefore can use a mutex-less memory allocator. TSVN uses multiple
> threads and has to use a memory allocator which uses mutexes. And those
> are much slower.

Are you saying the lock operation is still going on in the background after the window is closed? Correct me if I'm wrong, but I thought most TSVN windows did not allow you to close them until the operation was done (like the "OK" would be grayed out).

So at what point should the user expect TortoiseProc.exe to close?



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