-
Notifications
You must be signed in to change notification settings - Fork 60
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
Comments
Unfortunately this doesn't help because the call stack has no debug info. Can you retry the same with a debug build? |
I just noticed the error-message wasn't included in raze.log
My PC is compiling raze right now, I'll post the results asap. |
I added |
Unfortunately not. The crashing threas reports this: As you can see there's no function names. |
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. |
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, |
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. |
@Switch123456789, can you please see whether the commit (34129e8) in #1009 has fixed your issue? |
@mjr4077au I checked but unfortunately it's still crashing. |
I'm now having the exact same issue on release 1.9.1, also on Arch. |
I recently replaced my GTX 1060 (6GB) with a RX 6800 and did a fresh arch-install. |
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. |
This fixed all games for me, on older versions this wasn't an issue. |
That's the first bit of info that is really helpful. Will check ASAP. |
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
The text was updated successfully, but these errors were encountered: