While you're here, please consider supporting GamingOnLinux on:
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Steam Controller 2 is apparently a thing and being 'tooled for a mass production' plus a new VR controller
- Unofficial PC port of Zelda: Majora's Mask, 2 Ship 2 Harkinian has a big new release out
- Half-Life: Blue Shift remake mod Black Mesa: Blue Shift - Chapter 5: Focal Point released
- Linux kernel 6.12 is out now with real-time capabilities, more gaming handheld support
- Steam Deck OLED: Limited Edition White and Steam Deck Australia have launched
- > See more over 30 days here
-
Wine 9.22 released noting the 'Wayland driver enabled i…
- whizse -
Wine 9.22 released noting the 'Wayland driver enabled i…
- WMan22 -
Atari acquires Transport Tycoon from Chris Sawyer
- Milanium -
Fedora KDE gets approval to be upgraded to sit alongsid…
- Milanium -
The Sci-Fi Shooters Humble Bundle is a top deal with Sy…
- Arehandoro - > See more comments
- Weekend Players' Club 11/22/2024
- StoneColdSpider - Types of programs that are irritating
- kokoko3k - Our own anti-cheat list
- Liam Dawe - Spare gog keys
- on_en_a_gros - What do you want to see on GamingOnLinux?
- dpanter - See more posts
View PC info
I've been getting the "game crashed with signal sigsegv(11): segmentation fault" error in Total War Warhammer 2 for a very long time but it has increased in frequency since the last patch in January to the point where campaign battles are unplayable. The game crashes predictably, save games become corrupted and crash with the same error when loading them.
I'm running an all AMD rig. Ryzen 1700, RX 580 and 15 GB of ram. I also have an SSD and an HDD.
Online searches for "Total War Warhammer 2 segmentation fault" yield numerous other reports of the same problem but no solution. Has anyone managed to fix this or go around it in some other way?
I've seen people saying that the game works well through Proton but I really don't want to do that because what's the point of Feral Games ports then?
Thanks for your time.
Last edited by devland on 27 May 2022 at 11:19 am UTC
View PC info
View PC info
View PC info
I've been running the game with no more segfault crashes for over a week.
Last edited by ninjarlz on 5 March 2023 at 6:39 pm UTC
View PC info
I'm now trying to limit the cpu that the game uses by running
sudo cpulimit -e TotalWarhammer2 --limit 1200
after the game has started.
Note that the "1200" value is the equivalent of 75% max cpu usage since I have 16 cores and the max value for me is 1600. Check what the max value is for you by running "cpulimit --help".
For me the crash never happened on end turn. Only on the loading screen after battles or sometimes during a battle. But always when the cpu was in high usage so that's why I'm now trying the cpulimit thing.
Last edited by devland on 5 March 2023 at 10:38 pm UTC
View PC info
I gave up on trying to fix it.
The worst part is that it affects Total War Warhammer III as well. The problem can be traced back to Feral Total War Linux ports from 10 years ago.
Such a shame...