Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Fatal error on game launch #1006

Open
Switch123456789 opened this issue Oct 29, 2023 · 14 comments
Open

[BUG] Fatal error on game launch #1006

Switch123456789 opened this issue Oct 29, 2023 · 14 comments
Labels
bug Something isn't working OS-specific Issues specific to a particular OS version or distro

Comments

@Switch123456789
Copy link

Switch123456789 commented Oct 29, 2023

Raze version

1.8pre-928-g8545a2e74

Which game are you running with Raze?

All

What Operating System are you using?

Linux x86_64 (arch)

Relevant hardware info

Ryzen 3600 / GTX 1060 (6GB)

A clear and concise description of what the bug is.

All versions from the past 2-3 months of raze crash with the same error-message. It happens to every game (I tested all compatible games), I also tried it with a fresh config, with and without wayland enabled. I can see an empty window appear and a second later raze crashes.

raze.ini
raze.log
raze-crash.log

@Switch123456789 Switch123456789 added the bug Something isn't working label Oct 29, 2023
@coelckers
Copy link
Member

Unfortunately this doesn't help because the call stack has no debug info. Can you retry the same with a debug build?

@Switch123456789
Copy link
Author

I just noticed the error-message wasn't included in raze.log

*** Fatal Error ***
!!! Failed to exec debug process
Segmentation fault (core dumped)

My PC is compiling raze right now, I'll post the results asap.

@Switch123456789
Copy link
Author

I added -D CMAKE_BUILD_TYPE=Debug as a cmake parameter and ran raze with the gdb-command, I hope that is correct? I am inexperienced when it comes to developing and compiling, please give me a pointer if I missed something.
raze.log
raze-crash.log
gdb.txt

@coelckers
Copy link
Member

Unfortunately not. The crashing threas reports this:
Thread 1 (Thread 0x7fbf0bad2f40 (LWP 31472) "raze"):
#0 0x00007fbf0d5181c7 in wait4 () at /usr/lib/libc.so.6
#1 0x000055f9aae7989d in ()
#2 0x00007fbf0d45c710 in () at /usr/lib/libc.so.6
#3 0x000055f9ab0e24ec in ()
#4 0x000055f9ab0e0d1d in ()
#5 0x000055f9ab0e2ce8 in ()
#6 0x000055f9aaf739c8 in ()
#7 0x000055f9aaf77197 in ()
#8 0x000055f9aaf77d85 in ()
#9 0x000055f9aaf7e207 in ()
#10 0x000055f9aaf7eb5d in ()
#11 0x000055f9aae51084 in ()
#12 0x00007fbf0d445cd0 in () at /usr/lib/libc.so.6
#13 0x00007fbf0d445d8a in __libc_start_main () at /usr/lib/libc.so.6
#14 0x000055f9aae78d35 in ()
[Inferior 1 (process 31472) detached]

As you can see there's no function names.

@Switch123456789
Copy link
Author

I am sorry I can't assist any further here, the only documentation I found is from the zdoom wiki that is linked in the readme. I followed the instructions but it doesn't work, I searched online for 2 hours now but I can't find any information about how to debug raze.

@coelckers
Copy link
Member

I don't need you to debug it, but to compile a debug build and run that. The least I need is a call trace with symbol names,

@Switch123456789
Copy link
Author

Isn't running a debug build part of debugging? I tried to do what you said but again, I can't find documentation and I don't have enough knowledge. If the build-type-flag isn't enough to compile a debug build, then I don't know what is.

@mjr4077au
Copy link
Member

@Switch123456789, can you please see whether the commit (34129e8) in #1009 has fixed your issue?

@Switch123456789
Copy link
Author

@mjr4077au I checked but unfortunately it's still crashing.

@daemonspudguy
Copy link

I'm now having the exact same issue on release 1.9.1, also on Arch.

@Switch123456789
Copy link
Author

I recently replaced my GTX 1060 (6GB) with a RX 6800 and did a fresh arch-install.
Now some games are actually working again, I tried all compatible games and those are the ones that still don't work:
BLOOD: One Unit Whole Blood BLOOD: Cryptic Passage
Redneck Rampage Redneck Rampage Rides Again Redneck Rampage: Suckin' Grits on Route 66
NAM Platoon Leader

@SirFritz
Copy link

I managed to fix this (for me only blood was affected) by renaming each file in the blood folder to lowercase. It may be an issue with the case sensitivity in linux.

@Switch123456789
Copy link
Author

Switch123456789 commented Jan 16, 2024

renaming each file in the blood folder to lowercase

This fixed all games for me, on older versions this wasn't an issue.

@coelckers
Copy link
Member

That's the first bit of info that is really helpful. Will check ASAP.

@sinisterseed sinisterseed added the OS-specific Issues specific to a particular OS version or distro label Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working OS-specific Issues specific to a particular OS version or distro
Projects
None yet
Development

No branches or pull requests

6 participants