Re: [TSVN] Re: Another Possible Commit Memory Leak

Bill Reister wrote:
> 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?

 From the TSVN context menu, goto Settings and click on the [Edit]
button to edit the Subversion config file. You should find some
commented out entries for auto-props. This fragment comes from my config
file:

[miscellany]
enable-auto-props = yes

[auto-props]
*.c = svn:eol-style=native
*.h = svn:eol-style=native
*.txt = svn:eol-style=native
*.jpg = svn:mime-type=image/jpeg
*.bmp = svn:mime-type=image/bmp

What Stefan is referring to is that when you add *new* files with these
extensions, the properties will then get set automatically.

> 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.

Go to subversion.tigris.org. V1.2.3 has just been released but only as
a zip. The installer version is still at 1.2.1.

<http://subversion.tigris.org/files/documents/15/24487/svn-1.2.1-setup-2.exe>

The command line you need is:
svn commit -m "Log message" C:\my\working\copy

Obviously you need to put in the real (fully qualified) path to your
working copy, and a better log message.

> 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
> TortiseProc.exe.

TortoiseProc.exe is linked against the subversion client library which
does the subversion magic. The Subversion command line client is also
linked against those same libraries, so if they both show the same
symptoms the problem must lie in the client library. If the CL client
behaves differently, the problem lies within TSVN.

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org