frequent System.Threading.Tasks crashes w/ macOS Big Sur #250
Comments
|
Hello @jaz2038, thanks for reporting this! Since you say you've "upgraded to" Big Sur, can I assume this is an Intel-based Mac, and not one of the new Apple Silicon M1 Macs? Assuming this is an Intel Mac, can you please check if the following file exists: Assume it does exist, are you running any anti-virus software, or running in a VM (or is there something "interesting" with your setup)? |
mjcheetham
added
platform:osx
|
yes correct, intel based Macbook Pro (15" 2019). |
|
@mjcheetham I see same errors w/ and w/o antivirus running. |
|
Hi @jaz2038, from the limited searching I've done it seems the specific error message coming from the .NET Runtime "A device attached to the system is not functioning" is due to an unknown I/O failure at the runtime-OS layer ( I'm not entirely sure how to go about debugging this issue further. Can you try any/all of the following:
I hate suggesting the latter option. Might also be interesting to reach out on the dotnet/runtime repository about help with this? |
|
@mjcheetham thx for looking deeper here - #1/reinstalling didn't help. As for #2, I'm actually building several .net apps that aren't hitting this. Yeah I'm hesitant to try out #3/nuclear option but I can reach out to dotnet/runtime to see if there is any possible help there. If you have any other builds you'd like to try, I'm game for beta testing/getting more debug information for you as well. |
|
@mjcheetham I have a 100% repro on this. Every |
@johnterickson: a clarification, please: do you mean first attempt per shell session? Does it repro with a new Terminal tab, or restarting Terminal app? Or do you need to restart the computer? |
|
Great question @derrickstolee. Of course, by saying the above I was able to jinx it and it won't happen. I think it has something to do with time and/or sleep. I will try to repro. What logs info should I be capturing? Also, if I can get a repro, I will try excluding the GCM Core folder from Mac Defender and see if that is the key. |
|
@derrickstolee Ok the 100% (3/3) repro is to reboot and immediately try to By adding |
|
I am experiencing a similar issue, albeit when pushing to GitHub for a project unrelated to .NET Core development. Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'System.Threading.Tasks, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. A device attached to the system is not functioning.
(0x8007001F)
File name: 'System.Threading.Tasks, Version=4.1.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
at System.Diagnostics.ProcessWaitState.WaitForExit(Int32 millisecondsTimeout)
at System.Diagnostics.Process.WaitForExitCore(Int32 milliseconds)
at System.Diagnostics.Process.WaitForExit()
at Microsoft.Git.CredentialManager.Interop.Posix.PosixEnvironment.TryLocateExecutable(String program, String& path)
at Microsoft.Git.CredentialManager.EnvironmentExtensions.LocateExecutable(IEnvironment environment, String program)
at Microsoft.Git.CredentialManager.CommandContext..ctor()
at Microsoft.Git.CredentialManager.Program.Main(String[] args)
error: /usr/local/share/gcm-core/git-credential-manager-core get died of signal 6Any suggestions to help resolve this issue would be much appreciated. |
This did it for me, as I was running defender as well. |
|
The solution by @johnterickson worked perfectly for me:
You should be good to go. |
|
I am not running Microsoft Defender, so I remain uncertain how to resolve this issue. |
|
I have added the exception, and still see the issue in about 3:4 git interactions. |
|
I'm suffering from the same issue. My organization isn't using Microsoft Defender but Sophos but the issues are very similar. Running git-credential-manager-core a couple of times results in different errors until at some point it just works. Then after a while the issue comes back and I need to run it again a couple of times before it magically fixes itself. |
|
@mjcheetham Problem is definitely related to use of antivirus (ESET in my case) - by temporarily disabling realtime protection everything works fine. Latest errors look slightly different w/ the latest version of git-credential-manager-core that moved to .net 5 (2.0.374-beta+161775c536):
|
|
There are known issues with |
|
same issue on Big Sur 11.2.3 |
|
I should have been more clear but check 11.3.3 |
|
@aaroncrespo thx a ton - upgrading to Big Sur 11.3 Beta 3 fixes the issue for me. |
|
@johnterickson great tip - that seems to be helping with me so far. (Big Sur 11.2.3, Intel Mac with Microsoft Defender running.) |
|
Appears to be fixed with a newer .NET, Defender, and/or Big Sur release 😁 |
Which version of GCM Core are you using?
Git Credential Manager version 2.0.289-beta+22bd06dc57 (macOS, .NET Core 3.1.10)
From a terminal, run
git-credential-manager-core versionand paste the output.Which Git host provider are you trying to connect to?
Can you access the remote repository directly in the browser using the remote URL?
From a terminal, run
git remote -vto see your remote URL.[Azure DevOps only] What format is your remote URL?
{org}@dev.azure.com/{org}/...{org}.visualstudio.com/...[Azure DevOps only] If the account picker shows more than one identity as you authenticate, check that you selected the same one that has access on the web.
Expected behavior
I am authenticated and my Git operation completes successfully.
Actual behavior
About 1/5 times after I do a git pull or git push, I get this crash - I didn't see this until I updated to macOS Big Sur (originally seen this with macOS 11.0.1, still seeing it with macOS 11.1). After the crash I have to reauthenticate
(where xxx is my repo name)
Logs
Set the environment variables
GCM_TRACE=1andGIT_TRACE=1and re-run your Git command. Review and redact any private information and attach the log.The text was updated successfully, but these errors were encountered: