I've read the FAQ's and the bug log, seen similar bugs reported as "fixed" but
this may still be new. Under most circumstances, people would not update this
many files before a commit so I'm definitely a "problem user" lol! Sorry for
long post but wanted to give maximum info to identify problem.
Version: TortoiseSVN 1.2.1, Build 3895
I did a very large update to svn:mime-type for local copy of files:
==> Batch File <==
dir *.png /b/s > png.txt --create file with list of files to modify properties
on svn propset svn:mime-type image/x-png --targets png.txt -- set the mime-type
del png.txt -- clean up after yourself!
==> End Batch File, 5000+ files updated <==
Then I attempted a commit from the project root. First window came up
displaying list of modified files; selected OK to commit. 15 minutes later,
memory use for Tortise rapidly climbing past 2GB RAM on my laptop (which,
incidentally, has 2GB of real RAM so had was swapping and disk thrashing).
I'm guessing that this is a bit more memory use than one would expect for the
update; it was certainly more memory than the combined sizes of the files
(mostly thumbnails).
Experimented a bit, and the memory runaway only seems to start if in the
vicinity of 500 files are selected for commit. Below the magic number (sorry,
didn't get very precise), memory use grows quickly and stabilizes just before
commit window starts listing committed files. Above that number memory use
continues to grow unabated. Also noted that pressing "cancel" does not seem to
terminate the runaway condition.
Otherwise a great tool; hope this helps make it perfect!
Thanks,
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Aug 31 08:11:54 2005