Bill Reister wrote:
> Thanks for the quick response. Couple of answers & questions:
> Stefan Küng <tortoisesvn <at> gmail.com> writes:
> To avoid running such script, you should now set the autoprops in the
> config file. Otherwise you'll have to run that script again really
> soon ;)
> ==> Do you mean on the server side? Sorry, I'm a user not an
> administrator - if this is what you mean I'll have the admin
> set. Can you provide a sample of the autoprops file entries
> with an example of the lines needed to set props automatically?
No, that config file is client side. In the settings dialog, there's a
button "edit config file". Click on it and the Subversion config file is
opened in the default text editor. In that file, you'll find enough
comments to get you started ;)
If you still have questions, feel free to ask.
> Was the progress dialog already up? Or was still the dialog shown
> where you select the files for commit?
> ==> The progress dialog came up empty, and the memory started growing.
Ok, in that case, TSVN already executed the Subversion command.
> Did you select *all* the files shown there or did you exclude some of
> them from the commit?
> ==> Selected all. And the memory growth was associated with
> TortiseProc.exe process.
Of course. TSVN is linked against the Subversion library. So if the
memory use is high in the library, the memory use of the TSVN process grows.
> That seems to indicate the memory growth is happening in the progress
> dialog. In that case, it's a leak in Subversion, not TSVN.
> If you can, please try the CL client. If the memory grows there too,
> please report it on the Subversion mailing list.
> ==> Not sure where to get the CL client, or how to use to
> "disprove" Tortise as the culprit.
> I re-created this morning, and I made a mistake in my report.
> Runaway occurs in the vicinity of 5,000, not 500 files. Commited
> 2,200 files and memory grew to 350MB before progress dialog
> began to scroll. It may be that no actual runaway happened per-se;
> but just that my computer slowed down tremendously because of
> disk swapping when I ran out or physical memory. Therefore it
> may not actually be a leak but simply amazing memory use. Should
> memory use be this high (350MB = 2,200 files to commit)? I can't
> see how it would be SubVersion if the process that grows is
You can get the CL client from here:
Either use the setup.exe or just the zipped binary package.
Then, execute the command
svn commit path/to/working/copy -m "logmessage"
and watch the memory usage.
But maybe it's issue #1964 you're running into?
(again, that's a Subversion issue, outside of TSVN's scope).
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Aug 31 16:50:48 2005