You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you run the ssh-allocatepty example on windows, and monitor the open handles by that process, you'll notice that each session leaves ~1 file handle behind.
On linux, everything seems to work fine.
Here's how I'm monitoring this:
linux
# in one shell:
watch -n1 'ls -l /proc/$(pidof ssh-allocatepty)/fd | wc -l'# in another:whiletrue;do ssh -p2222 localhost; sleep 1;done
windows
# in one shell:while(1) { cls; Get-Process|Where-Object {$_.Name-like"ssh-allocatepty"}; sleep 1}
# in another (the first column is the number of Handles open)while(1) { cls; ssh -p 2222 localhost; sleep 1}
The text was updated successfully, but these errors were encountered:
If you run the
ssh-allocatepty
example on windows, and monitor the open handles by that process, you'll notice that each session leaves ~1 file handle behind.On linux, everything seems to work fine.
Here's how I'm monitoring this:
linux
windows
The text was updated successfully, but these errors were encountered: