protonscr

Steam Client Freeze after launching a game with Proton

steamclosed Steam clientProton
ValveSoftware/steam-for-linux#6387 · opened 2019-07-13 by VortexAcherontic · updated 2019-07-18 · 1 comments · github
1 matching comments, n / p to jump
VVortexAcherontic 2019-07-13 github

Since the latest Steam client and Proton updates I'm encountering freezes of the Steam client when launching a game via Proton.

System Specs:

  • OS: openSUSE Leap 15.1 (Kernel: 4.12.14 with driver and security back ports done by suse from 4.19 Kernels) [Leap kernel string: 4.12.14-lp151.28.7-default]
  • GPU: GeForce GTX 1080 (Driver: 430.26)
  • CPU: AMD Ryzen 7 1800X
  • RAM: 16 GB
  • Steam Library 1: [HDD] XFS (Volume 235,8 GiB free of 1,8 TiB total) (Default Library)
  • Steam Library 2: [SSD] XFS (Volume 159,9 GiB free of 931,1 GiB total) (Home folder)
    System information - Gist !Translated from German to English!
    Terminal output - gist

Firth I thought this might be caused by older games I'm running with D9VK 0.13 (first noticed this after testing D9VK 0.13) but even games which where running fine with D9VK 0.12 are now freezing. Also I tried if this happens with any game using DXVK or Wine D3D but same story. The whole steam client freezes after a few seconds in game and will finally crash and don't resume.

This dose not happen with any native Linux games.

Games I tested (and causes the issue):

  • The Void
    -- D9VK 0.13 AND Wine D3D
    -- Proton 4.2-9

  • Dragons Dogma: Dark Arisen
    -- D9VK 0.12 / Wine D3D
    -- Proton 4.2-9 (D9VK only) / 3.16-9 (Wine D3D)

  • BioShock Remsatered
    -- DXVK
    -- Proton 4.2-9

  • HITMAN: Blood Money
    -- D9VK 0.13
    -- Proton 4.2-9

  • Elite Dangerous: Horizons
    -- DXVK
    -- Proton 4.2-9

  • DOOM 2016
    -- Vulkan
    -- Proton: 4.2-9

  • Borderlands 2
    -- D9VK 0.12 / 0.13
    -- Proton 4.2-9

Any game making use of the Steam API did freeze as well and crashed toghether with the steam client as well. Except of Doom 2016. It got stuck in the loading screen but still running and playing music until the steam client died and took Doom with him.

Further more I was not able to find any matching issue belonging to this.
How ever I found something which was addressing this issue to some File system issues and a possible work around would be preloading inode64 when parts of a file are above a 32bit address range for the file system. How ever I use Steam in conjunction with XFS file systems for about 3 years now and was never encountering issues even not on very full drives but I still mentioned it here because I'm not sure if this is somewhat related.

Please let me know if I can provide any further information on this topic. :)

VVortexAcherontic 2019-07-18 github

I feel like this issue could be closed because today I just deleted my whole steam config folder (~/.local/share/Steam) except of the steamapp folder and the issue did not reappeared. Maybe over the years the steam installation lived through 3 different version of my distro is allowed to have odd settings :D

Proton versions