Rise of the Tomb Raider crash on start

Hyper_Eye

At the end of November I purchased Tomb Raider and Rise of the Tomb Raider. Both games worked fine. Recently I tried to start Rise of the Tomb Raider and it crashes. Tomb Raider works fine. Other vulkan games like Serious Sam Fusion and The Talos Principle work fine. Proton using DXVK works fine. For the life of me I can't figure out what is wrong with Rise of the Tomb Raider. I have seen no other reports of this issue.

The game launcher starts fine. I click Play, I get a black flash or black window (depending on whether I have it configured for windowed or fullscreen) and then I get an error dialog that indicates a sigsegv occured. I have looked at the log and the dump file and it doesn't tell me squat.

I have tried:

I get the same crash no matter what I do. If anyone has the game and can try it I would appreciate it. I would also appreciate any suggestions. I have a similar problem with all Saints Row games that other people don't seem to have but I would like to tackle these one at a time. All of the other native games I have in Steam work.

The Main Man · Posted: Fri Mar 20, 2020 11:59 pm Post subject:

Same problem here but it works fine in Proton, not just fine but better

Hyper_Eye · Posted: Sat Mar 21, 2020 12:19 am Post subject:

The Main Man · Posted: Sat Mar 21, 2020 12:29 am Post subject:

Hyper_Eye · Posted: Sat Mar 21, 2020 12:30 am Post subject:

What version of glibc do you have installed?
_________________
Gentoo Gaming Videos

The Main Man · Posted: Sat Mar 21, 2020 8:40 am Post subject:

The Main Man · Posted: Sat Mar 21, 2020 10:18 am Post subject:

Hey, I got it working now, but you have to do this each time you start it.
When that configuration dialog appears try to select 800x600 resolution and check 'Run in a window' checkbox.
Then once in the game from the game options change it back to the resolution you want and fullscreen.
I tried it numerous times and that's the only way I can make it to work.
Trying for example 1920x1080 with 'Run in a window' also doesn't work.
Didn't try resolutions between 1920x1080 and 800x600, also 800x600 but with 'Run in the windows' unchecked.
To summarize ... 800x600 running in a window works and the game runs normally after that, it has to be done every time.

You probably tried that already but that's my experience with this game at the moment.

sebaro · Veteran Joined: 03 Jul 2006 Posts: 1141 Location: Romania

Same here, SIGSEGV(11) with the native port, fine with Proton/DXVK.

AMDGPU, kernel 5.4, mesa 19/20, glibc-2.29-r7.

Last time it worked was before the profile migration from 17.0 to 17.1.

'Run in a window' workaround doesn't work for me.

The Main Man · Posted: Wed Mar 25, 2020 11:25 am Post subject:

btw I removed glibc compile option , it was needed for Borderlands and Kotor II, but since I can't remember the last time I played those games I removed that, recompiled glibc and tried Tomb Raider and it worked, so it's not that either.
amdgpu, kernel 5.5.11, mesa 20.0.2, glibc 2.30-r6

I made a video, I don't know what else I can tell you guys, wish I can help you more.
https://streamable.com/hcyfl

Once again, if I start it 1920x1080 fullscreen it doesn't work
Plus, it happens maybe once out of 10 times that it's not working even with this trick, but on another launch it works again.

The Main Man · Posted: Mon Apr 06, 2020 11:49 am Post subject:

Works now without that window trick.
I just launch it and it starts 1920x1080 fullscreen, no problems.
There was a problem first time when I tried it, there was sound but no visuals, I killed it and then start it again, it worked.
Then I exited normally from the game and try to launch it 5 times, it worked each time.
So, there is a problem sometimes, but in my case when that happens next launch is okay.

EDIT:
btw I get this when there's a bad launch

Chiitoo · Posted: Mon Apr 06, 2020 12:43 pm Post subject: ><)))°€

The Main Man · Posted: Mon Apr 06, 2020 12:58 pm Post subject: Re: ><)))°€

sebaro · Veteran Joined: 03 Jul 2006 Posts: 1141 Location: Romania

This is about Rise Of The Tomb Raider (2016) not Tomb Raider (2013).

The Main Man · Posted: Tue Apr 07, 2020 8:32 am Post subject:

Damn, I feel stupid :oops:

Thanks for explaining it.

swanson · Posted: Mon Apr 13, 2020 3:04 pm Post subject:

Funnily enough, I'm having the same issue after testing all games after an AMD RX470 to RX5700 upgrade and thought it might be a driver issue but reverting didn't resolve. Played successfully last summer before this testing.

Most of the Feral games crash dumps are Windows type minidumps and you need to use minidump-2-core to convert to normal core files. So from my latest crash;

$ minidump-2-core ~/.local/share/feral-interactive/Rise\ of\ the\ Tomb\ Raider/crashes/archived/abc123.dmp > /tmp/rise.core
$ cd ~/.local/share/Steam/SteamApps/common/Rise\ of\ the\ Tomb\ Raider
$ gdb bin/RiseOfTheTombRaider /tmp/rise.core

And then backtrace;

sebaro · Veteran Joined: 03 Jul 2006 Posts: 1141 Location: Romania

With "gdb RiseOfTheTombRaider"

Hu · Administrator Joined: 06 Mar 2007 Posts: 22673

Did you use the same CFLAGS for both builds of sys-libs/glibc?

sebaro · Veteran Joined: 03 Jul 2006 Posts: 1141 Location: Romania

swanson · Posted: Wed Apr 15, 2020 11:36 pm Post subject:

Just to confirm, you're saying you have actually tested reverting to glibc-2.29-r2 and ran the game successfully?

If so, then comes the joy of finding which patch(s) added in glibc-2.29-r7 patchset glibc-2.29-patches-8.tar.xz from glibc-2.29-r2 patchset glibc-2.29-patches-3.tar.xz caused the problem.
_________________
Alan.

sebaro · Veteran Joined: 03 Jul 2006 Posts: 1141 Location: Romania

Hyper_Eye · Posted: Thu Apr 16, 2020 4:31 pm Post subject:

Maybe they will surprise you but there is a chance they will respond by saying that Gentoo is not a supported platform. They have done so before.
_________________
Gentoo Gaming Videos

swanson · Posted: Thu Apr 16, 2020 7:53 pm Post subject:

Well, didn't think it likely, but reverting to glibc-2.29-r2 does not fix the issue.
_________________
Alan.

Hu · Administrator Joined: 06 Mar 2007 Posts: 22673

Did you revert by reinstalling a previously built tbz2 or by building the -r2 version again? If the latter, then environmental changes (such as a different compiler versio or CFLAGS) could be relevant. If the former, then that would seem to rule out glibc entirely.

swanson · Posted: Fri Apr 17, 2020 4:44 pm Post subject:

The latter; rebuilding glibc-2.29-r2 within the current environment. This is assuming glibc is the issue which we can't really tell from the backtrace which is the main problem.

RoTR doesn't appear to have had any patches since 2018 and checking my emerge log the major changes for me since last summer are glibc-2.28-r5 to glibc-2.29-r2 in June and gcc-8.3.0 to gcc-9.2.0 in August but can't confirm exact time last played successfully and sebaro just (?) believes it last worked with glibc-2.29-r2. My CFLAGS haven't changed AFAICR but gcc/glibc ebuild/eclass strip most out anyway.

Anyway, I have a few things to try this weekend from my with borgbackups.
_________________
Alan.

swanson · Posted: Sat Apr 18, 2020 4:58 pm Post subject:

And the problem is ALSA 1.2.2.

Just resolved a problem with Dying Light also not running by reverting from alsa-lib-1.2.2 to alsa-lib-1.2.1.2. And sure enough, retesting RoTR it now runs successfully.

Dying Light uses libfmodex64.so while the RiseOfTheTombRaider binary appears to have it statically linked so there must be some ALSA incompatibility/bug (assuming we're non-PulseAudio users) and that might be an ongoing issue as FMOD EX is dead and won't ever be updated. Nothing obvious in the ALSA changelog so need to bisect.

EDIT: Looks to be ALSA bug 27 fixed by commit conf: change the order of PCM devices in alsa.conf. So should be fixed in ALSA 1.2.2.1 or 1.2.3 whenever released.
_________________
Alan.