Stackdumps

[Sven]

I'm working on two different machines, both running Windows XP Pro
(one SP2, the other SP3). On both of them I am experiencing very
frequent stackdumps and related errors when running git commands.
Example:

C:\projects\news>git pull
0 [main] sh.exe" 1032 open_stackdumpfile: Dumping stack
trace to sh.exe.stackdump
^CTerminate batch job (Y/N)? y

C:\projects\myproject>git pull
0 [main] sh.exe" 2920 open_stackdumpfile: Dumping stack
trace to sh.exe.stackdump
0 [main] sh.exe" 3288 open_stackdumpfile: Dumping stack
trace to sh.exe.stackdump
^CTerminate batch job (Y/N)?

These happen perhaps 80% of the time when I run certain commands.
Usually I can get away with commits, diffs, and adds, but merge,
branch, and stash commands are all prone to these crashes, and push
and pull commands even more so. These network commands furthermore
suffer ssh crashes.

I have been upgrading msysGit as new versions come out. I was most
recently on Git-1.5.6.1-preview20080701.exe, but I just tried
Git-1.6.0.2-preview20080921.exe in the hope of a solution.
Unfortunately the problems persist. Nearly every time I do a commit I
have to delete an sh.exe.stackdump file, and these crashes are clearly
leaking some important system resource, as my system becomes slower
and less stable as the day wears on, a condition only (temporarily)
relieved by a reboot.

I've hunted around for solutions to this. I've heard about troublesome
Logitech drivers, but I don't have them. I've heard about problems
with malware, but the latest scans are finding none. I've heard about
conflicts with Cygwin, and I've tried taking that out of my path to no
avail.

I am aware that this problem might be more of an MSYS affliction than
a Git affliction, but it's with msysGit that I'm experiencing them. I
love developing with the tools that Git gives me, but these issues are
an infuriating and significant distraction from my core work. Can
anyone here offer guidance?

-Sven

[Johannes Sixt]

On Montag, 22. September 2008, Sven wrote:
> I'm working on two different machines, both running Windows XP Pro
> (one SP2, the other SP3). On both of them I am experiencing very
> frequent stackdumps and related errors when running git commands.
> Example:
>
> C:\projects\news>git pull
> 0 [main] sh.exe" 1032 open_stackdumpfile: Dumping stack
> trace to sh.exe.stackdump
> ^CTerminate batch job (Y/N)? y

Just a shot in the dark: Have you tried disabling the virus scanner?

-- Hannes

[Sven]

On Sep 22, 3:17 pm, Johannes Sixt <johannes.s...@telecom.at> wrote:
> Just a shot in the dark: Have you tried disabling the virus scanner?
>
> -- Hannes

I hadn't actually tried it, Hannes. I am running McAffee VirusScan on
one machine and AVG on the other. So I just tried a rebooting my
machine for a clean start, disabling the on-access scanner, and doing
a git pull. Unfortunately I got the same sort of stack dump the first
time. When I get back to the other machine I'll try disabling AVG, but
there's obviously still something else that can cause these crashes.
Thank you for the suggestion, though. It was worth a try!

-Sven

[Sven]

On Sep 22, 1:33 pm, Sven <Sven....@gmail.com> wrote:
> Usually I can get away with commits, diffs, and adds, but merge,
> branch, and stash commands are all prone to these crashes, and push
> and pull commands even more so. These network commands furthermore
> suffer ssh crashes.

I happen to have a convenient example of one of these, so let me offer
the details:

C:\projects\myproject>git push

[Dialog box pops up labeled "ssh.exe - Application Error":
The instruction at "0x7105be73" referenced memory at
"0x00000000". The memory could not be "read".
[OK / Cancel]

After dismissing the popup I find the command shell window blocking,
but I can CTRL-C to terminate the batch job that's still running. Task
Manager will sometimes reveal sh.exe, ssh.exe, or git still running in
this situation.

-Sven