Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When I open Git Bash from the Explorer context menu, Explorer stops responding, regardless whether the folder is a Git folder. Immediately when I close Git Bash, Explorer starts to respond again.

My system is running Windows 7 Professional x64 and the Git version is 1.9.0.msysgit.

Do you have any idea what could be causing this? Here is a gif describing the problem: enter image description here

share|improve this question
create a dump of the Explorer, open the dump in WinDbg and run !analyze -v -hang. Copy & paste the Windbg output to pastebin and post a link here – magicandre1981 Mar 20 '14 at 18:56
@magicandre1981 and how would I go about doing that? – Gaui Mar 21 '14 at 15:42
Use Taskmgr or ProcessExplorer to generate the dump. Windbg is part of the WinSDK (Debugging Tools) – magicandre1981 Mar 21 '14 at 19:10
up vote 9 down vote accepted

It looks like it is a problem with the git-cheetah extension with git 1.9.0.

A recent change made for FarManager makes Git Cheetah capture stderr/stdout even when we are not interested in it, to avoid cluttering FarManager's precious console. Due to this workaround, Git Bash makes the Explorer -- Git Cheetah's primary intended consumer -- hang.

It looks like the fix has been commited to the codebase but as to when it will appear in the git update I have no idea!

share|improve this answer

I can confirm that uninstalling / reinstalling with:

[x] Windows Explorer integration
   (*) Simple context menu (Registry based)
      [x] Git Bash Here
      [x] Git GUI Here
   ( ) Advanced context menu (git-cheetah plug-in)

...solved the problem for me under Windows 8.1 while keeping the functionality I needed. Thanks to Justin for the real answer; sorry I don't have the rep yet to make this just a comment.

share|improve this answer
Confirmed, using simple context menu (registry-based) instead of advanced context menu (git-cheetah plugin), works. – Gaui Mar 28 '14 at 10:52

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .