I’m assuming you’re talking about Cryobyte increasing swap size, which was actually necessary for some games. God of War for example has a memory leak on devices with an integrated cpu/gpu (so handhelds and most laptops), and it would cause a full system lockup and crash after 30min-1hr of playtime. The memory leak would eventually stop around 17.5-18.5 GB of total RAM + VRAM used. Increasing swap file size would let the game run without issues or crashes.
That specific use case shouldn’t be needed anymore since Valve switched to ZRAM.
I 100% had this issue, I could watch the combined memory climb towards 17GB over a play session, and when it got close the system would lock up. This was on an LCD deck, and I was targeting a 30fps with some of the graphical texture settings on high iirc. Some people reported being able to play the game fine, and my best guess is that they were targeting a higher frame rate and had graphical textures turned down. Since the memory leak would eventually stop growing, it’s possible that with low enough settings you might be able to stay under the crash threshhold.
The other possibility is that since it only would crash after playing for awhile, that short play sessions might let you get through without issue. The length of the sessions before a crash would probably be longer the lower your texture settings.
Fubarberry@sopuli.xyz 4 weeks ago
I’m assuming you’re talking about Cryobyte increasing swap size, which was actually necessary for some games. God of War for example has a memory leak on devices with an integrated cpu/gpu (so handhelds and most laptops), and it would cause a full system lockup and crash after 30min-1hr of playtime. The memory leak would eventually stop around 17.5-18.5 GB of total RAM + VRAM used. Increasing swap file size would let the game run without issues or crashes.
That specific use case shouldn’t be needed anymore since Valve switched to ZRAM.
kadup@lemmy.world 4 weeks ago
Fubarberry@sopuli.xyz 4 weeks ago
I 100% had this issue, I could watch the combined memory climb towards 17GB over a play session, and when it got close the system would lock up. This was on an LCD deck, and I was targeting a 30fps with some of the graphical texture settings on high iirc. Some people reported being able to play the game fine, and my best guess is that they were targeting a higher frame rate and had graphical textures turned down. Since the memory leak would eventually stop growing, it’s possible that with low enough settings you might be able to stay under the crash threshhold.
The other possibility is that since it only would crash after playing for awhile, that short play sessions might let you get through without issue. The length of the sessions before a crash would probably be longer the lower your texture settings.