[1.1.110] Crash on launch

[sanddune]

I am unable to launch the latest version of Factorio because it crashes immediately everytime.
- Launching through Steam: It does not launch and nothing seems to happen.
- Launching through command line I get the following: "[1] 12113 segmentation fault (core dumped) ./factorio".
- Launching with gdb I get the following:

Code: Select all

Program received signal SIGSEGV, Segmentation fault.
0x0000000001ee4510 in std::codecvt<char16_t, char, __mbstate_t>::do_unshift(__mbstate_t&, char*, char*, char*&) const ()
(gdb) bt
#0  0x0000000001ee4510 in std::codecvt<char16_t, char, __mbstate_t>::do_unshift(__mbstate_t&, char*, char*, char*&) const ()
#1  0x00000000016681f2 in std::__detail::_BracketMatcher<std::__cxx11::regex_traits<char>, false, false>::_M_ready() ()
#2  0x000000000166fd24 in void std::__detail::_Compiler<std::__cxx11::regex_traits<char> >::_M_insert_bracket_matcher<false, false>(bool) ()
#3  0x00000000016466a9 in std::__detail::_Compiler<std::__cxx11::regex_traits<char> >::_M_atom() ()
#4  0x000000000160f7c6 in std::__detail::_Compiler<std::__cxx11::regex_traits<char> >::_M_alternative() ()
#5  0x0000000001590f0c in std::__detail::_Compiler<std::__cxx11::regex_traits<char> >::_M_disjunction() ()
#6  0x00000000016465c3 in std::__detail::_Compiler<std::__cxx11::regex_traits<char> >::_M_atom() ()
#7  0x000000000160f7c6 in std::__detail::_Compiler<std::__cxx11::regex_traits<char> >::_M_alternative() ()
#8  0x000000000160f87b in std::__detail::_Compiler<std::__cxx11::regex_traits<char> >::_M_alternative() ()
#9  0x000000000160f87b in std::__detail::_Compiler<std::__cxx11::regex_traits<char> >::_M_alternative() ()
#10 0x0000000001590f0c in std::__detail::_Compiler<std::__cxx11::regex_traits<char> >::_M_disjunction() ()
#11 0x0000000001b0aa8f in std::__detail::_Compiler<std::__cxx11::regex_traits<char> >::_Compiler(char const*, char const*, std::locale const&, std::regex_constants::syntax_option_type) [clone .constprop.0] ()
#12 0x0000000001b21f01 in std::__cxx11::basic_regex<char, std::__cxx11::regex_traits<char> >::_M_compile(char const*, char const*, std::regex_constants::syntax_option_type) [clone .constprop.0] ()
#13 0x0000000001a926ae in std::__cxx11::basic_regex<char, std::__cxx11::regex_traits<char> >::basic_regex(char const*, std::regex_constants::syntax_option_type) [clone .constprop.0] ()
#14 0x00000000006644ad in __static_initialization_and_destruction_0() [clone .lto_priv.0] ()
#15 0x0000000001f8dced in __libc_csu_init ()
#16 0x00007ffff7740ea4 in __libc_start_main_impl (main=0x60df10 <main>, argc=1, argv=0x7fffffffc9a8, init=0x1f8dca0 <__libc_csu_init>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffc998)
    at ../csu/libc-start.c:343
#17 0x00000000006a57f9 in _start ()

There is no crash log generated in "~/.factorio/".

I have tried:
- Deleting and reinstalling the game.
- Deleting "~/.factorio".
- Downloading the game directly from the site.
- Disabling steam overlay.

I've tried multiple versions and the latest version of the game that still launches is 1.1.104.

System Info:
- Linux Kernel 6.10.10-arch1-1 (64-bit)
- Display Server: x11
- Graphics: Nvidia 3080
- CPU: AMD 7950X
- Audio: Pipewire

[scolton]

I'm seeing something similar (same stacktrace), with similar specs. Have you managed to get anywhere? I saw a very vague statement somewhere on a seemingly unrelated SIGSEGV issue that led me to believe it might have something to do with the AMD driver, but it seems like that's not the likely culprit here given the difference in our GPUs.

Kernel: 6.10.10-arch1-1 (also doesn't work on 6.6.56-1-lts -- same problem)
Display Server: X11
Graphics: Radeon 7900 XTX
CPU: AMD 5950X
Audio: Pipewire

[DeHackEd]

Nope, this is happening during early initialization of libraries. With only the backtrace to work with, my gut says that Factorio is statically linked against libstdc++ but something dynamically linked is also using libstdc++ from your own system. There's a compatibility mismatch and it blows up.

Is there any chance you can upgrade libstdc++, and/or GCC, on your system?

[scolton]

I'm fully up-to-date -- gcc and gcc-libs are the following version: 14.2.1+r134+gab884fffe3fc-1. Do you have a suggestion for a version to try?

[scolton]

Okay I think you're onto something. My laptop was still working with Factorio -- ostensibly because it was set up with an ancient Arch mirror that hadn't synced since June. After updating on a current mirror, everything is broken.

I've tried downgrading packages as follows, but there were literally a thousand packages that updated, so I'm not sure which one caused the problem:

Code: Select all

[2024-10-12T18:37:28-0500] [ALPM] downgraded gcc-libs (14.2.1+r134+gab884fffe3fc-1 -> 14.1.1+r58+gfc9fb69ad62-1)
[2024-10-12T18:37:29-0500] [ALPM] downgraded gcc (14.2.1+r134+gab884fffe3fc-1 -> 14.1.1+r58+gfc9fb69ad62-1)
[2024-10-12T18:43:29-0500] [ALPM] downgraded glibc (2.40+r16+gaa533d58ff-2 -> 2.39+r52+gf8e4623421-1)
[2024-10-12T18:43:30-0500] [ALPM] downgraded lib32-glibc (2.40+r16+gaa533d58ff-2 -> 2.39+r52+gf8e4623421-1)
[2024-10-12T18:47:16-0500] [ALPM] downgraded lib32-gcc-libs (14.2.1+r134+gab884fffe3fc-1 -> 14.1.1+r58+gfc9fb69ad62-1)
[2024-10-12T18:48:30-0500] [ALPM] downgraded libc++abi (18.1.8-4 -> 17.0.6-1)
[2024-10-12T18:48:30-0500] [ALPM] downgraded libc++ (18.1.8-4 -> 17.0.6-1)

I've attached the full list of packages that were updated in hopes that one will stand out as a potential problem-causer...

[scolton]

Updating to 2.0.8 seems to have fixed it for me.

[sanddune]

Version 2.0.8 appears to have fixed it for me as well.