search

guberm / tortoisegit

Automatically exported from code.google.com/p/tortoisegit
0 stars 0 forks source link

Explorer.exe high CPU usage when viewing repository #2193

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Open task manager
2. Clone any repository
3. Open the root folder using windows explorer

What is the expected output? What do you see instead?
Explorer.exe's cpu usage should stay low. Instead, it goes up to 10% on a 24 
core machine, eating a whole 2 core and a half.

What version of TortoiseGit and msysgit are you using? On
what operating system?

v1.8.8.0 with git 1.9.2.msygit.0 on Windows 8.1 update 1 x64

Original issue reported on code.google.com by Kawazoe.Masahiro on 17 May 2014 at 7:08

GoogleCodeExporter commented 9 years ago 
What overlay setting (Status cache) have you set?

Have you checked out what explorer.exe does (e.g. by using ProcMon (Process 
Monitor))?

Original comment by sstrickr...@googlemail.com on 18 May 2014 at 11:19

GoogleCodeExporter commented 9 years ago 
I am experiencing the same issue. Explorer becomes completely unresponsive, and 
I can't even close Explorer windows. Additionally, when I navigate to the root 
of a repository that causes this, *all* Explorer processes begin consuming 
multiple cores. Killing the offending Explorer process causes the others to 
return to idle. Interestingly, TGitCache does not significant CPU usage.

I have TortoiseGit 1.8.6.0 w/msysgit 1.8.4.msysgit.0. My overlay settings were 
"Default", which uses TGitCache. When I set them to "Shell" or "Shell 
Extended", the problem goes away.

I attached a debugger and confirmed that Explorer had called into TortoiseGit 
to compute overlays.

Original comment by mtay...@sigovs.com on 30 May 2014 at 11:33

GoogleCodeExporter commented 9 years ago 
Can you spot the location in the code which causes the high load?

Original comment by sstrickr...@googlemail.com on 30 May 2014 at 11:42

GoogleCodeExporter commented 9 years ago 
capture a xperf trace of the CPU usage:

http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-42-WPT-CPU-Analysis

The data from the Debugger are only a snpshot, so you don't know if this is 
really the cause.

Original comment by MagicAnd...@live.com on 6 Aug 2014 at 7:57