Commit dialog becomes unresponsive after hitting F5 to refresh

By atna... on September 30, 2010 03:28 (imported from Google Code)

---

What steps will reproduce the problem?

There are two ways to reproduce this and both have different dependencies. I'll call them "Problem 1" and "Problem 2".

Steps to reproduce problem Problem 1:

1. Preparation:
   > MKDIR C:\problem1
   > CD /D C:\problem1 && ECHO. >a.txt
   > git init

2. Open C:\problem1 in Explorer and open TortoiseGit's commit dialog.

3. Hit F5 to refresh.

Steps to reproduce Problem 2:

1. Preparation:
   > MKDIR C:\problem2\folder
   > CD /D C:\problem2 && ECHO. >folder\b.txt
   > git add folder\b.txt && git commit -m initial
   > ECHO changed >folder\b.txt

2. Open C:\problem2 in Explorer and open TortoiseGit's commit dialog.

3. Hit F5 to refresh.

What is the expected output? What do you see instead?
Expected output is a refreshed commit dialog. (In this case, the same as what was initially shown.) Instead, TortoiseProc becomes unresponsive after displaying "Please wait...".

What version of the product are you using? On what operating system?

Problem 1 can be reproduced in these following versions:
TortoiseGit-1.5.3.0-32bit & Git-1.7.0.2-preview20100309 = YES
TortoiseGit-1.5.6.0-32bit & Git-1.7.0.2-preview20100309 = YES
TortoiseGit-1.5.7.0-32bit & Git-1.7.0.2-preview20100309 = YES
TortoiseGit-1.5.3.0-32bit & Git-1.7.2.3-preview20100911 = UNTESTED
TortoiseGit-1.5.6.0-32bit & Git-1.7.2.3-preview20100911 = UNTESTED
TortoiseGit-1.5.7.0-32bit & Git-1.7.2.3-preview20100911 = YES

Problem 2 can be reproduced in these following versions:
TortoiseGit-1.5.3.0-32bit & Git-1.7.0.2-preview20100309 = NO
TortoiseGit-1.5.6.0-32bit & Git-1.7.0.2-preview20100309 = YES
TortoiseGit-1.5.7.0-32bit & Git-1.7.0.2-preview20100309 = YES
TortoiseGit-1.5.3.0-32bit & Git-1.7.2.3-preview20100911 = UNTESTED
TortoiseGit-1.5.6.0-32bit & Git-1.7.2.3-preview20100911 = UNTESTED
TortoiseGit-1.5.7.0-32bit & Git-1.7.2.3-preview20100911 = YES

Operating system is Windows XP Professional 32-bit (Japanese).

Please provide any additional information below.

• Executing "tskill git" will make the commit dialog responsive again.

• In the unresponsive state, Process Explorer (by Sysinternals) shows:

For Problem 1:
explorer.exe -> TortoiseProc.exe -> git.exe:
Path: C:\Program Files\Git\bin\git.exe
Command line: "C:\Program Files\Git\bin\git.exe" ls-files -s -t -z
Current directory: C:\problem1\
Threads: (no threads are shown)
Handles:
Directory \Windows
Directory \KnownDlls
File C:\problem1
File \Device\NamedPipe\Win32Pipes.00000f88.0000001d
File \Device\NamedPipe\Win32Pipes.00000f88.0000001d
Key HKLM
KeyedEvent \KernelObjects\CritSecOutOfMemoryEvent

For Problem 2:
explorer.exe -> TortoiseProc.exe -> git.exe:
Path: C:\Program Files\Git\bin\git.exe
Command line: "C:\Program Files\Git\bin\git.exe" diff-index --raw HEAD --numstat -C -M -z
Current directory: C:\problem2\
Threads: (no threads are shown)
Handles:
Directory \Windows
Directory \KnownDlls
File C:\problem2
File \Device\NamedPipe\Win32Pipes.00000e74.00000017
File \Device\NamedPipe\Win32Pipes.00000e74.00000017
Key HKLM
KeyedEvent \KernelObjects\CritSecOutOfMemoryEvent

It looks like git.exe is in a suspended state before (or maybe after?) execution.