There are no svn:externals in these working copies.
I had Status cache set to Shell. Now I changed it to None. So far I
haven't had the problem after making this change. I'll keep testing though
to make sure.
> 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?
> Are you referencing a large number of svn:external properties in
> your working copy? I recently submitted a patch to address
> an issue where TCP connections were not cleaned up until process
> exit. This problem caused similar "lockup" behavior under
> Windows. This patch did not make it into 1.6.6.
> You may want to try and disable the TortoiseSVN icon cache process as well,
> since it can bog things down on large working copies. (I don't
> consider 1.2G all that large though.)
> Kevin R.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-23 19:50:38 CEST