@kisak-valve anything I can do to help on troubleshooting this one? A memory leak on CEF looks to me like a pretty important thing that can affect multiple games.
The latest Steam OS update did not help on this issue. CEF is still being OOM'd:
[Thu Feb 2 00:53:39 2023] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/[email protected]/app.slice/gamescope-session.service,task=CrBrowserMain,pid=53458,uid=1000
[Thu Feb 2 00:53:39 2023] Out of memory: Killed process 53458 (CrBrowserMain) total-vm:10075176kB, anon-rss:3921812kB, file-rss:0kB, shmem-rss:18028kB, UID:1000 pgtables:11128kB oom_score_adj:200
[Thu Feb 2 00:53:39 2023] systemd-journald[718]: Data hash table of /var/log/journal/6fc4ed751616403ea7eaf3dc5c0ddc00/system.journal has a fill level at 75.0 (8534 of 11377 items, 6553600 file size, 767 bytes per hash table item), suggesting rotation.
[Thu Feb 2 00:53:39 2023] systemd-journald[718]: /var/log/journal/6fc4ed751616403ea7eaf3dc5c0ddc00/system.journal: Journal header limits reached or header out-of-date, rotating.
[Thu Feb 2 00:53:39 2023] input: Steam Deck as /devices/pci0000:00/0000:00:08.1/0000:04:00.4/usb3/3-3/3-3:1.2/0003:28DE:1205.0004/input/input34
[Thu Feb 2 00:53:40 2023] oom_reaper: reaped process 53458 (CrBrowserMain), now anon-rss:0kB, file-rss:0kB, shmem-rss:16796kB
It's launching now, but it crashes randomly during gameplay. Not sure if I should even bother sending a new proton log for a ticket that's dead in the water.
Game was running fine so far but now it's just stuck when I press play. Tried with Proton 8.0-4 and Proton Experimental. Using mesa 23.2.1 on Arch now. Tried on kernels LTS 6.1.25 and 6.6.0-rc4.
steam-1573280.log
Hello @Patola, your Proton log shows DXVK seeing mesa/RADV and AMDGPU-Pro. As a quick test, can you see how the game behaves if it only can use mesa/RADV?
err: DxvkSubmissionQueue: Command submission failed: -13 looks like a possible line of interest from your log.
That was incredible. Using launch parameters vk_radv %command% the game now starts correctly. So that's what was happening! Thank you, @kisak-valve
proton 8.0-4x1 2023-10proton experimentalx1 2023-10
Compatibility Report
System Information
I confirm:
Symptoms
When launched on the Steam Deck, the game takes some time launching then crashes to a black screen. The Steam Deck environment crashes and is reloaded (ssh sessions at the time still persist). Seems like a memory (RAM and not VRAM) issue, but minimum specs for the game are 8GB. The oom-killer message says the offending process is CrBrowserMain at almost 10GB, and this is not even a process from the game -- it's from Chrome Embedded Framework. These are the messages on
dmesgat the time of crash:steam-1573280.log
Reproduction
Notes