WW2 Rebuilder (appid 1573280)

Compatibility Report

• Name of the game with compatibility issues: WW2 Rebuilder
• Steam AppID of the game: 1573280

System Information

• GPU: Steam Deck APU (AMD ATI AMD Custom GPU 0405)
• Driver/LLVM version: Mesa 22.2.0.157821.radeonsi_3.4.0_2-2
• Kernel version: 5.13.0-valve36-1-neptune
• Link to full system information report as Gist: https://gist.github.com/Patola/d29b74a9d55dde17d3c652302c182780
• Proton version: 7.0-5

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

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 dmesg at the time of crash:

[15805.533257] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service/app.slice/gamescope-session.service,task=CrBrowserMain,pid=8727,uid=1000
[15805.533390] Out of memory: Killed process 8727 (CrBrowserMain) total-vm:9914672kB, anon-rss:3717564kB, file-rss:0kB, shmem-rss:19988kB, UID:1000 pgtables:10876kB oom_score_adj:200
[15806.125882] oom_reaper: reaped process 8727 (CrBrowserMain), now anon-rss:0kB, file-rss:0kB, shmem-rss:18656kB

steam-1573280.log

Reproduction

• Just install and try to play the game. It will take a couple minutes loading, then it will crash to a black screen.

Notes

• steam topic/post about this issue: https://steamcommunity.com/app/1573280/discussions/0/5946474365644122637/?tscn=1674092738
• the game works fine on my desktop with Arch Linux / 32 GB / Ryzen 9 5900X / AMD RX 6800 XT GPU. I can bring logs from it and even my laptop with nvidia if it makes debugging this issue easier.
• Crashes the same way in desktop mode too (steam crashes with it, the interface remains).

Start by reproducing the crash on Steam Deck and inspect steam-1573280.log alongside the reported dmesg OOM-killer messages. No source file or entry point is identified; done would require determining the cause of the CrBrowserMain memory failure and confirming that the game no longer crashes to a black screen.