.Disconnect hangs the thread on MacOS
See original GitHub issuevar ssh = new SshClient(hostName, username, password);
ssh.Connect();
var command = ssh.RunCommand("whoami");
Console.WriteLine($"Command result: {command.Result}");
ssh.Disconnect();
ssh.Dispose();
The above code runs fine on Windows but hangs on MacOS. It will connect and run the remote command just fine, but it never gets past the .Disconnect. If there is no .Disconnect, it will hang on .Dispose.
Tested with .NET Core 2.2 and 3.1 and v2016.1.0.
Downgrading to v2013.4.7 fixes the issue.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Mac OS hangs after disconnecting external display
Hi here what to do based on apple article: To disconnect your MacBook Pro or PowerBook G4 from the display after use:
Read more >If your Mac restarts and a message appears
If your Mac restarts unexpectedly, an error known as a “kernel panic” occurred.
Read more >7 Fixes to Try if Your Mac Gets Stuck Updating
1. Restart or Force Restart Your Mac ... The IT guy's solution to all your problems is a cliché for a reason. Restarting...
Read more >Google Chrome hangs/ crash for MacBook Air (2019) ...
Log out of my profile/ remove extensions; Tried it in safe mode but its still hanging; Reinstall Mac OS; when I tried to...
Read more >Fix Wi-Fi & Internet Connection Problems in macOS Ventura
1: Disable or Remove 3rd Party Firewall / Network Filtering Tools · Go to the Apple menu and choose “System Settings” · Go...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@delebru Please try 2020.0.0-beta1, and let me know it that fixed the issue for you.
See #355
Does the issue occur on the latest build on develop?