I started here because I was seeing the problem even when using the
command-line client exclusively, without even navigating the working copy in
Since changing the Status cache preference in TortoiseSVN fixed the problem,
I completely agree. :-)
On Fri, Oct 23, 2009 at 2:06 PM, Ryan Schmidt <
> On Oct 23, 2009, at 11:32, Justin Johnson wrote:
> I am running Windows XP SP3 with Subversion and TortoiseSVN 1.6.6 and have
>> 2 GB of RAM with nothing else running during the operations. The problem
>> below has also been seen in 1.6.3 and I've heard reports from users I
>> support that they've seen this in 1.5.x.
>> For sufficiently large working copies (1.2 GB, not sure what the cut off
>> is though) when performing update or status operations from the top level of
>> the working copy, Windows Explorer locks up and stops refreshing windows or
>> responding at all. This usually leads to errors in the actual Subversion
>> operation, saying there aren't enough resources to complete the operation.
>> Sometimes my VPN client disconnects part way through. For these large
>> working copies I can usually reproduce the error with one or two updates in
>> a row.
>> Sometimes I can clear it up by killing Windows Explorer and letting it
>> automatically reload.
>> Has anyone else seen issues like this? Is this a memory leak?
> Subversion itself has nothing to do with Windows Explorer. TortoiseSVN,
> being a windows shell extension, of course does, so I think you should talk
> to the developers of TortoiseSVN about this on their mailing list.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-23 21:22:46 CEST