[LINUX] New beta leaks X clients

[turol]

Newest beta continually creates and leaks X clients. This will eventually result in hitting the limit and being unable to open any new X programs until Steam has been closed.

See https://unix.stackexchange.com/questions/368017/cant-start-applications-due-to-maximum-number-of-clients-reached-error for command on how to check this.

[xrogaan]

Came here to say just that.

[Gunner Hans Schmulke]

Same issue.

[Tourfaint]

Github thread here, this has to be fixed asap
https://github.com/ValveSoftware/steam-for-linux/issues/9094

[No0815]

Took a while to troubleshoot my way through to this thread. Looks like the resources I came across on my way are already linked. So Steam is effectively unusable under Linux/X11 for the time being. I swear, if this is related to the Steam Awards ...
I'm almost certain their notifications already lead to issues over the last two weeks, where parts of Steam became completely unresponsive and I had to send a sigterm.

[dzlls.Dr.AmmarkoV]

Same here!

[badgersocks]

Yep, hugely leaky as of this last one. Needs fixing ASAP.

[Raiman]

Same issue, opted out of the Beta.
Having to use htop to send a sigkill to one of the many zombies the webhelper or trayicon leave behind has been "normal" for me for some time. It's been rather cumbersome to just restart Steam since it won't if there is a zombie somewhere that signals steam its already running.

[Niklaws]

can confirm, creates new x client every few seconds
with the default maximum being 256 this leads to an unusable system rather quickly

[I88I]

Same thing here, happens only on Beta.

[Rosentti]

If only the client could be ported to wayland. Seems like every time valve fixes a bug with steam, a new bug takes it's place. Using -gamepadui seems to work around most issues (freezing on nvidia wayland, freezing on notification), but it didn't work around this.

[nodesai]

Confirming this report. I noticed it when I couldn't launch other apps. Seems to leak faster when I put steam in the background and toggle it to foreground. This continues until all connections are used up.
I track it using this:
watch -n 1 "lsof -U +c 15 | cut -f1 -d' ' | sort | uniq -c | sort -rn | head -5"

[CidDaBird]

They said there will be a fix soon. More likely today.

[LinuxLogicGamer]

Ok, I'm not the only one having this problem

[*BURRRP!*]

This has been driving me crazy since yesterday! The output in

journalctl -f

could fill a turn-of-the-century novel! I guess I won't be gaming until this is updated :/

[badgersocks]

Originally posted by *BURRRP!*:

This has been driving me crazy since yesterday! The output in

journalctl -f

could fill a turn-of-the-century novel! I guess I won't be gaming until this is updated :/

I turned off beta and rolled it back for now, and everything's flawless.