Bug#1007822: "ssh -XAf localhost xeyes" uses 100% CPU after losing tty

Ralf Jung <[email protected]>
Newsgroups gmane.linux.debian.devel.ssh
Message-ID <57ae9e8b-927e-a341-e351-2e671432b6a5__14766.4853882574$1648082552$gmane$org@ralfj.de>
Hi all,

I am also seeing 100% CPU load from SSH when using it with autossh to set up 
port forwarding in the background (no X11 forwarding involved):

/usr/bin/autossh -M 0 -N -o "ServerAliveInterval 30" -R $IP:$PORT1:localhost:443 
-R $IP:$PORT2:localhost:80 $USER@$HOST -i $KEY

This only recently started with the latest 'apt upgrade'.

; Ralf

On Thu, 17 Mar 2022 13:26:09 +0100 Harald Dunkel <[email protected]> wrote:
> Package: openssh-client
> Version: 1:8.9p1-3
> 
> If I use
> 
> 	ssh -XAf localhost xterm
> 
> to run a second xterm, then ssh eats up 100% CPU after closing the
> first xterm.
> 
> Same happens for xeyes or other XWindow apps. It doesn't have to be
> localhost, either.
> 
> "nohup ssh -XAf ..." seems to work, but for Bullseye it works very well
> without nohup.
> 
> SHELL is bash 5.1-6
> 
> 
> Regards
> Harri
> 
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.