Games with steams built in proton will take about 45 Minutes to launch

[MartinKurtz]

Proton Version is 9, Ive tried 9.0-4 and UMU 9.0-3.2 so faras well as experimental and hotfix. This issue does not occur when launching through lutris with the same proton version, and only when using the steam client with proton as compatibility tool enabled. After Launch, the game plays fine. During launch the steam client will diplay launching and after abpout 25 minutes running. after that it takes about 20 minutes more for the game to actually launch

computer Info:

Manufacturer: ASRock
Model: Z370 Killer SLI
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
CPU Family: 0x6
CPU Model: 0x9e
CPU Stepping: 0xc
CPU Type: 0x0
Speed: 4900 MHz
8 logical processors
8 physical processors
Hyper-threading: Unsupported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Debian GNU/Linux 12 (bookworm) (64 bit)
Kernel Name: Linux
Kernel Version: 6.1.0-23-amd64
X Server Vendor: The X.Org Foundation
X Server Release: 12201009
X Window Manager: KWin
Steam Runtime Version: steam-runtime_0.20240806.97925
Video Card:
Driver: AMD AMD Radeon RX 6750 XT (navi22, LLVM 15.0.6, DRM 3.49, 6.1.0-23-amd64)
Driver Version: 4.6 (Compatibility Profile) Mesa 22.3.6
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x1002
DeviceID: 0x73df
Revision Not Detected
Number of Monitors: 3
Number of Logical Video Cards: 1
Primary Display Resolution: 3840 x 2160
Desktop Resolution: 7740 x 2400
Primary Display Size: 27.56" x 15.35" (31.54" diag), 70.0cm x 39.0cm (80.1cm diag)
Primary VRAM: 12288 MB
Sound card:
Audio device: USB Mixer
Memory:
RAM: 32028 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: de_DE.UTF-8
Total Hard Disk Space Available: 1874720 MB
Largest Free Hard Disk Block: 1620927 MB
Storage:
Number of SSDs: 3
SSD sizes: 2000G,0B,0B
Number of HDDs: 0
Number of removable drives: 0

a log file of game launch of this happening:
https://drive.proton.me/urls/G0CCDNPHE0#3jZqwBEVvUwo

What else can i provide to give you as much information as possible?

[kisak-valve]

Hello @MartinKurtz, give ValveSoftware/steam-runtime#323 a read and check if you're seeing a similar soft file limit snafu.

[MartinKurtz]

I do not think i am affected by it, as ulimit -Hn returns 1048576 and -Sn 1024 for me, but ive applied the fix/workaround recommended there anyway as duckduckgo says it shouldnt hurt me, but this does not seem to fix the issue, why should it, the limits are the same as what they already were. How would i know for sure?

[spiffeeroo]

Your log has this warning:
WARNING: Low /proc/sys/vm/max_map_count: 65530 will prevent some games from working

Debian 12 uses the default value of 65530 for vm.max_map_count. Memory and resource intensive games like Baldur's Gate 3 will probably struggle at the default value.

Other Linux distributions like Fedora, Ubuntu 24.04 LTS, and Arch have changed this default value to 1048576. SteamOS on the Steam Deck has vm.max_map_count set to 2147483642. Probably use the default max_map_count value used by Fedora for a general purpose computer.

Try sudo sysctl --write vm.max_map_count=1048576 in a terminal. Then test the game again.

For a permanent fix, create a file at /etc/sysctl.d/90-override.conf containing:
vm.max_map_count = 1048576
which will apply at every boot.

Edit: Some games (like God of War 2018) may run slower because of the Linux kernel's split lock detection.
https://www.phoronix.com/news/Linux-Splitlock-Hurts-Gaming

Since Debian 12 is on kernel 6.1, you can only change this through a kernel parameter of split_lock_detect=off. Newer kernels can change this through sysctl interface with split_lock_mitigate=0.

[MartinKurtz]

ive applied that fix, since it was throwing a error, but the vm.max_map_count doesnt seem to have been all of the issue, although the game now goes from launching to running in under a second, though the second "phase" still takes some 20 odd minutes.

I do not think i am affected by the split lock issue, as in game performance is perfectly fine, it is just the startup time that is an issue.

Will provide a new log later, but now i wanna play the game and restarting the game takes so long