Aha - yes, we are running windows 64 bit server. We use subversionnotify
for pre-commit hooks but by default there is a post commit hook that I
guess could be doing a diff so this looks very promising. When 1.7.2 is
released via SVN Edge I'll re-instate the post commit hook (just to
test).

Thanks for the response Mark.

 

Thanks also to Stefan & Markus who also pointed out that it was not SVN
that calls svnlook.exe - I removed the post commit hook (not used
anyway) and so far so good.

 

Paul Hester



 

From: Mark Phippard [mailto:markp...@gmail.com] 
Sent: 11 November 2011 13:40
To: Hester, Paul
Cc: users@subversion.apache.org
Subject: Re: Client commit hangs, server svnlook.exe hogs CPU

 

On Fri, Nov 11, 2011 at 3:06 AM, Hester, Paul <paul.hes...@cobham.com>
wrote:

        Since upgrading to 1.7.0, and 1.7.1 via subversion edge, about
half the commits being done by users (via tortoise) result in the commit
hanging after most of the work has been done. Whilst hung, the
repository shows the commit has taken place, but on the server
svnlook.exe is hogging all the CPU. Killing the svnlook.exe process
allows the commit to continue (normally).

 

Is the server Windows 64-bits?

 

There is an infinite loop bug that is fixed for 1.7.2 that can occur on
Windows 64-bit with diff algorithm.  So if you are making a diff for a
post-commit email or something like that it could be that you are
running into.


-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/


This e-mail and any files transmitted with it ("E-mail") is intended solely for 
the addressee(s)
and may contain confidential and/or legally privileged information. If you are 
not the addressee(s), any
disclosure, reproduction, copying, distribution or other use of the E-mail is 
prohibited. If you have received
this E-mail in error, please delete it and notify the sender immediately via 
our switchboard or return e-mail.

Neither the company nor any subsidiary or affiliate or associated company nor 
any individual sending this E-mail
accepts any liability in respect of the content (including errors and 
omissions) nor shall this e-mail be deemed
to enter the company or any subsidiary or affiliate or associated company into 
a contract or to create any
legally binding obligations unless expressly agreed to in writing under 
separate cover and timeliness of the
E-mail which arise as a result of transmission. If verification is required, 
please request a hard copy version
from the sender.

Reply via email to