[BUG] [Exhumed] Segmentation fault

[michaelneverwins]

Raze version

Raze 1.10.2

Which game are you running with Raze?

Exhumed/Powerslave

What Operating System are you using?

Linux x86_64

Please describe your specific OS version

Linux Mint 21.3

Relevant hardware info

Intel CPU, AMD Radeon HD 7950

Have you checked that no other similar issue already exists?

• I have searched and not found similar issues.

A clear and concise description of what the bug is.

I recently built (per GZDoom build instructions with some adjustments as necessary) and installed Raze 1.10.2, and I've noticed that Exhumed is crashing frequently. It doesn't seem to happen in the same spot every time, but I haven't been able to complete the first level.

I thought maybe switching to OpenGL mode might fix it, given my old GPU's questionable Vulkan support and the fact that some recent versions of Raze (or at least portable builds not compiled by me) didn't seem to want to run in Vulkan mode at all on my machine (see #1017), but I temporarily switched to OpenGL and it still crashed.

I'd be concerned that I just messed up in building Raze somehow, except I'm quite sure that Duke Nukem 3D, Blood, and Shadow Warrior are all unaffected. I'll definitely come back to correct myself if I find out that I'm wrong, but I think I've played them enough that I would have seen them crash by now, given how frequently Exhumed crashes. So as of now I believe this is a game-specific issue.

Attached are my last crash log and my configuration file.

Steps to reproduce the behaviour.

Explain how to reproduce

1. Build and install Raze 1.10.2 on Linux.
2. Play the first level of Exhumed (with non-free data from GOG version if that could possibly matter).

Your configuration

raze.ini.txt (renamed)

Provide a Log

raze-crash.log

[michaelneverwins]

I decided to try quick-saving frequently while playing through the first level. I hoped that this would allow me to progress despite frequent crashing, and that maybe later levels would be less prone to these crashes. However, I got myself to a point where the game will almost always crash a few seconds after loading my save even if I do nothing.

I don't know if this will help in reproducing the issue on other systems, but the save file in question is attached:
save0000.zip
(Note that this Zip file is the save file itself renamed from save0000.dsave to save0000.zip, because GitHub won't let me upload it with the original extension and file save0000.dsave identifies the file type as Zip archive data. So just rename it back to save0000.dsave instead of unzipping it, unless you actually want to see the insides.)

On one occasion, as I repeatedly loaded the save to verify the consistency of this behavior while writing this comment, it didn't crash (at least not right away, and I was able to walk around a bit and create another save from which I will do more testing). I don't know why it was different in that case. But I think it's safe to say that it crashes within 3 to 4 seconds of loading the attached save at least 90% of the time.

[mauriciocc]

I was facing some crashing now and then during the gameplay (normally when i got hit by a mummy and turn), but when a get to this part of the game i was unable to go thought, crashes all the time.

• Map: Alien Mothership
• Raze 1.10.2
• OS: Windows 11
• Hardware: Ryzen 5 5600x, 1080 Ti
• CrashReport.zip
• raze.ini
• save0000.zip

[michaelneverwins]

I had some free time and decided to try compiling some older versions. I haven't tested this extensively, but Raze 1.10.1 and Raze 1.10.0 also crashed as I played through the first level, while Raze 1.9.1 seems more stable. I was able to play through the first level with 1.9.1 without a crash, which seemed practically impossible with Raze 1.10.2 when I first opened this issue. I suppose I should also mention that I'm on Linux Mint 22 now, whereas I was on Linux Mint 21.3 before, but I don't think it makes any difference considering that the 1.10.x versions still seem to be crashing.