[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Critical bug: explorer.exe CPU consumption

From: Matthew Ratzloff <matt_at_builtfromsource.com>
Date: 2007-01-25 19:32:30 CET


Ever since I started using TortoiseSVN about a year ago, I've had the same
issue. This issue occurs on both my home and work Windows XP machines. I'm
using the latest version, 1.4.1.

Whenever I update or check out a large repository (hundreds of files), I
have to kill the explorer.exe process. That's because CPU usage immediately
jumps to 99%--there's a direct correlation between the two events. The
problem is so severe that often the Task Manager refuses to come up until I
hit Ctrl+Alt+Delete multiple times. The files do not show up in the folder
view when I try to look at them; usually it makes the problem worse (Windows
becomes even less responsive). Small repositories do not have this effect.

After I kill all explorer.exe processes and start it again (run
explorer.exe), the problem immediately goes away. I can look at the files
in folder view, they have icon overlays, etc.

In an effort to at least isolate the problem, I tried to use separate
explorer.exe processes (from folder view: Tools | Folder Options | View |
Launch folder windows in a separate process). When I do this, the main
desktop GUI is the one that jumps to 99%. Once I kill that process, the
other one, the folder view, is unaffected. I have to kill it, though, to
restart explorer.exe to get the Start Menu and and desktop icons back.

Can you believe I still use TortoiseSVN?? I really like it in all other
respects, but this bug is just driving me up the wall. I upgrade
immediately each time, hoping that the bug will be fixed, but it's not.
Please help!



To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Jan 25 20:29:38 2007

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.