protonscr

[Overlay] - Quick Access Menu gets stuck on screen if toggled rapidly in Hollow Knight: Silksong

steamopen overlayDistro Family: SteamOS
ValveSoftware/steam-for-linux#12314 · opened 2025-09-08 by matte-schwartz · updated 2026-02-18 · 6 comments · github
Mmatte-schwartz 2025-09-08 github

Your system information

  • Steam client version (build number or date): 1757031224
  • Distribution (e.g. Ubuntu): SteamOS
  • Opted into Steam client beta?: Yes
  • Have you checked for system updates?: Yes (SteamOS 3.8)
  • Steam Logs: steam-logs-oled-deck.tar.gz
  • GPU: AMD Custom GPU 0932

Please describe your issue in as much detail as possible:

After launching the game Hollow Knight: Silksong and reaching the starting menu, if you rapidly toggle the Quick Access Menu several times in a row the QAM will get stuck on screen, and eventually crash steamwebhelper. This affects all of my SteamOS devices (Steam Deck, ROG Ally, Legion Go, MSI Claw).

Image

the main lines of note in my steam logs seem to be a spam of:

==> /home/deck/.steam/steam/logs/webhelper_js.txt <==
[2025-09-08 09:54:38] SteamUI: INFO: Trying to change focus to already selected tab
[2025-09-08 09:54:38] SteamUI: INFO: Trying to change focus to already selected tab
[2025-09-08 09:54:38] SteamUI: INFO: Trying to change focus to already selected tab
[2025-09-08 09:54:38] SteamUI: INFO: Trying to change focus to already selected tab
[2025-09-08 09:54:38] SteamUI: INFO: Trying to change focus to already selected tab
[2025-09-08 09:54:38] SteamUI: INFO: Trying to change focus to already selected tab
[2025-09-08 09:54:38] SteamUI: INFO: Trying to change focus to already selected tab
[2025-09-08 09:54:38] SteamUI: INFO: Trying to change focus to already selected tab
[2025-09-08 09:54:38] SteamUI: INFO: Trying to change focus to already selected tab
[2025-09-08 09:54:38] SteamUI: INFO: Trying to change focus to already selected tab

When this issue happens, both the Steam button and ... buttons do not respond to input as well.

Steps for reproducing this issue:

  1. Launch Hollow Knight: Silksong on a SteamOS device
  2. After reaching the main menu, start toggling the QAM
Mmatte-schwartz 2025-09-08 github

The issue does not seem to happen on the Steam Deck Stable client branch with the same OS version.

Mmatte-schwartz 2025-09-10 github

Looks like this bug made it into the latest Stable release (1757452101)

Mmatte-schwartz 2025-09-10 github

seems like a steamwebhelper memory leak occurs when it gets stuck as well, ballooning from ~500Mb to over 2Gb of memory usage and spiking CPU usage before the process itself crashes:

Image

One minute later:

Image
Mmatte-schwartz 2025-10-03 github

update notes mentioned something that sounded similar:

Fixed a crash in D3D12 games that could sometimes be triggered by opening and closing sections of the overlay (like notes) rapidly. This could manifest as a game or gpu hang, was easier to trigger in some games than others, and was a new regression in this week's public client update and the last beta cycle. We will test this briefly in beta before shipping as a hotfix to all users.

but the issue reported here persists:

https://github.com/user-attachments/assets/313e69d6-ab5c-4c40-807f-28f194b44155

Mmatte-schwartz 2026-02-18 github

I can still reproduce this issue on my Legion Go 2 with the latest Deck client beta (1771028361): steam-logs.tar.gz

this freeze seemed to be triggered after I switched the performance profile field from custom to low-power and then tried closing the QAM. this possibly only still affects non-Deck devices.

Mmatte-schwartz 2026-02-18 github

easiest steps to reproduce the issue now seem to be:

  1. Launch a game on a non-Deck device like the Legion Go 2 or Legion Go S
  2. Once in-game, rapidly switch between performance profiles

https://github.com/user-attachments/assets/361cd4ab-7c0e-47ce-92d7-41df5f37b1b3

Nothing extracted yet.