Re: why does my SVN client process die an hour after completion of commit?

Stefan Sperling <stsp_at_elego.de> writes:

> On Fri, Oct 21, 2011 at 10:34:52AM +0100, Jon Nicoll wrote:
>> So, my question is: is there something in the 'svn commit' protocol
>> which causes the client process to do a lot of work, potentially
>> causing the client machine to run out of memory, up to one hour after
>> the server has determined that a checkin is complete?
>
> This is a known issue in Subversion 1.6.
> Adding many files in one commit uses too much memory, see:
> http://subversion.tigris.org/issues/show_bug.cgi?id=1964#desc12

The reason it happens after a commit is complete on the server is that
the client has to modify the metadata for all the items in the working
copy that were committed. When the commit starts the items being
committed all have local modifications of some kind, when the commit is
complete they must all be change to unmodified. This can involve a lot
of work, writing pristine text and properties, updating the revision
numbers. This updating cannot happen until the client knows that the
commit was successful.

-- 
Philip