ST give stackup dump error ending in resource unavailable

git -c diff.mnemonicprefix=false -c core.quotepath=false pull origin alpha/release-631
0 [main] sh 12300 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
0 [main] sh.exe" 13120 sync_with_child: child 12300(0x170) died before initialization with status code 0xC0000005
11 [main] sh.exe" 13120 sync_with_child: *** child state waiting for longjmp
/usr/libexec/git-core/git-sh-setup: fork: Resource temporarily unavailable

This error just started cropping up for me.  If I delete the dump file, before I have a chance to test again, the dump file is simply recreated prior to the retest.  I'm running Windows 10 and have never seen this problem before. 

Initially it was just with one repo so after not being able to get past it yesterday I stepped away. Early this morning I tried that same repo again and was able to push my files up without incident.

My next task, different repo, was to pull down the most recent updates to a branch...and I get the same error in that repo.

The only changes in my environment were Windows 10 updates pushed to my computer from Microsoft.  I have not yet heard of anyone else on my team getting this error.

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Sunday in Feedback & Announcements

How do you analyze GC logs, thread dumps and head dumps?

Hi awesome community!  In this article, I would like to describe the one of the toolset (service) for the analyze some problems on different Java-based instances, of course, as Atlassian admini...

108 views 0 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you