RE: Update and Status in large working copy causes Windows to hang
Hi Stefan, -Original Message- From: Stefan Sperling [mailto:s...@elego.de] Sent: Monday, November 08, 2010 6:16 PM To: Jans Ullrich Cc: jus...@honesthacker.com; andy.l...@gmail.com; markp...@gmail.com; users@subversion.apache.org Subject: Re: Update and Status in large working copy causes Windows to hang Have you tried to reproduce the issue with command line clients provided by other vendors? See http://subversion.apache.org/packages.html#windows Hadn't tried until now. Please also try with version 1.6.13, if possible. I downloaded the most recent (1.6.13 at the time) command line client from Collabnet, tested it, same problem: insufficient resources. We did some more tests, ran the update while running procmon, didn't fail. (WTF?!) After running procmon, the issue didn't reappear on the machine we ran the tests on. We're now investigating what running procmon changed on the machine. (Nothing was installed, just the exe from sysinternals was run) Cheers, Ulli Please note: This e-mail may contain confidential information intended solely for the addressee. If you have received this e-mail in error, please do not disclose it to anyone, notify the sender promptly, and delete the message from your system. Thank you.
Re: Update and Status in large working copy causes Windows to hang
On Fri, Sep 10, 2010 at 08:14:24AM +, ullrich.j...@elektrobit.com wrote: TortoiseSVN works on both machines. (1.6.8, svn libs 1.6.11) Command line svn client creates the issue on machine B, not on machine A. Version of the command line client: 1.6.12, was also tested with 1.6.1 The compiled command line binary was downloaded from http://alagazam.net/ Have you tried to reproduce the issue with command line clients provided by other vendors? See http://subversion.apache.org/packages.html#windows Please also try with version 1.6.13, if possible. Thanks, Stefan
RE: Update and Status in large working copy causes Windows to hang
Hi, -Original Message- From: Johan Corveleyn [mailto:jcor...@gmail.com] Sent: Friday, September 10, 2010 1:24 PM Some quick questions from the hip: - What kind of disks are the working copies located on for machine A and B? Locally or remotely? The disks are in all cases local hard drives, no sharing. - For A and B: are they 32-bit or 64-bit? Both machines are 64 Bit machines, running XP 32 Bit - How big is the working copy we're talking about? Can you give an idea of the number of directories, the number of files, and the total disk space (excluding .svn dirs)? The working copy is about 2.0 GB (according to Windows taking up 2.54 GB on disk), 158515 files, 33471 folders (excluding .svn folders). I know this is large, but since it's working on one machine and not the other, it's still puzzling. Cheers, Ulli -- Ullrich Jans, Specialist, IT-A Phone: +49 9131 7701-6627, mailto:ullrich.j...@elektrobit.com Fax: +49 9131 7701-6333, www.elektrobit.com Elektrobit Automotive GmbH, Am Wolfsmantel 46, 91058 Erlangen, Germany Managing Directors: Otto Fößel, Jarkko Sairanen Register Court Fürth HRB 4886 Please note: This e-mail may contain confidential information intended solely for the addressee. If you have received this e-mail in error, please do not disclose it to anyone, notify the sender promptly, and delete the message from your system. Thank you.
Re: Update and Status in large working copy causes Windows to hang
On Fri, Sep 10, 2010 at 10:14 AM, ullrich.j...@elektrobit.com wrote: Hi. Now I'm getting bitten by this. -Original Message- From: Justin Johnson [mailto:jus...@honesthacker.com] Sent: Monday, October 26, 2009 9:39 PM Subject: Re: Update and Status in large working copy causes Windows to hang [...] Interesting, none the less. Thank you. I was still planning on trying to get Symantec AV disabled for testing purposes. Just posting my progress. :-) I'll post again with my results of that test, assuming I can convince someone to let me. In my case, disabling OfficeScan didn't help. I have the funny issue that two machines that are nearly identical except for the processor behave differently. Machine A: Intel Core2 Quad, 4 GB memory, running XP SP3: works. Machine B: Intel i7, 4 GB memory, running XP SP3: gets the issue with insufficient system resources. Findings we had: TortoiseSVN works on both machines. (1.6.8, svn libs 1.6.11) Command line svn client creates the issue on machine B, not on machine A. Version of the command line client: 1.6.12, was also tested with 1.6.1 Disabling hyperthreading on machine B has no effect. Disabling TurboBoost on machine B has no effect. It’s not a memory problem – the machine did not run out of memory, according to the windows performance counters. Running vmware player on machine A, svn update crashes on the host, works on the guest. Windows doesn’t quite hang, when the screen locks, you can still try to log on as Administrator, which logs off the subversion user and causes the machine to recover. I’m running out of ideas what else to try to get it running. Versions: APR 1.3.9 APR-util 1.3.9 APR-ICONV 1.2.1 Neon 0.28.6 Berkeley DB 4.4.20 OpenSSL 0.9.8o ZLib 1.2.3 Apache 2.2.15 Python 2.6 libintl 0.14.1 (patched) Ruby 1.8.6 Cyrus SASL 2.1.22 serf 0.3.0 sqlite 3.6.22 The compiled command line binary was downloaded from http://alagazam.net/ Some quick questions from the hip: - What kind of disks are the working copies located on for machine A and B? Locally or remotely? - For A and B: are they 32-bit or 64-bit? - How big is the working copy we're talking about? Can you give an idea of the number of directories, the number of files, and the total disk space (excluding .svn dirs)? Cheers, -- Johan
