Compatibility Report

• Name of the game with compatibility issues: Goose Goose Duck
• Steam AppID of the game: 1568590
• Steam build ID: 25329877

System Information

• Distribution: CachyOS
• GPU: AMD Radeon RX 6700/6700 XT/6750 XT class (Navi 22)
• Video driver version: Mesa 26.2.3
• Kernel version: 7.2.6-1-cachyos
• CPU: AMD Ryzen 5 5600
• RAM: 32 GiB
• Swap: 32 GiB zram
• Desktop/compositor: Hyprland 0.56.2, Aquamarine 0.15.1
• Link to full system information report as Gist: Not available yet; relevant system and kernel OOM details are included below.
• Proton version: Proton Experimental 11.0 (experimental-11.0-20260917b-x86_64; shown in Steam as Proton 11.0-2)

I confirm:

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

Symptoms

The game starts and is playable, but its memory usage grows without a practical limit. It eventually consumes about 25–26 GiB of resident RAM and about 29–30 GiB of swap. Once RAM and the 32 GiB zram swap are exhausted, the kernel OOM killer terminates the Goose Goose Duck process. Hyprland then segfaults in libaquamarine, ending the graphical session.

This occurred four times on September 25, 2026. At the OOM events, only 28–156 KiB of 32 GiB swap remained free.

Representative kernel records:

Free swap = 88kB / Total swap = 32761852kB
Out of memory: Killed process (Goose Goose Duc) total-vm:66614472kB, anon-rss:26664156kB, file-rss:67544kB, shmem-rss:9632kB
Hyprland: segfault in libaquamarine.so.0.15.1

Free swap = 36kB / Total swap = 32761852kB
Out of memory: Killed process (Goose Goose Duc) total-vm:65428008kB, anon-rss:26204192kB, file-rss:55708kB, shmem-rss:5956kB

Free swap = 156kB / Total swap = 32761852kB
Out of memory: Killed process (Goose Goose Duc) total-vm:68143052kB, anon-rss:27407312kB, file-rss:54256kB, shmem-rss:7276kB

Free swap = 28kB / Total swap = 32760828kB
Out of memory: Killed process (Goose Goose Duc) total-vm:68146504kB, anon-rss:27113508kB, file-rss:55968kB, shmem-rss:7772kB
Hyprland: segfault in libaquamarine.so.0.15.1

The OOM victim is the game process itself, not steam.exe or wine64. The issue reproduced after restarting the graphical session and the computer.

Reproduction

1. Force Proton Experimental / Proton 11.0-2 for Goose Goose Duck.
2. Start the game normally from Steam.
3. Play normally and monitor the Goose Goose Duck process.
4. Memory usage continues rising until both RAM and swap are exhausted.

Expected Result

Memory usage should remain bounded and the game should not trigger a system-wide OOM condition.