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.
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot