[3.7.1] Brutal Doom Black Edition 3.1d crashes on Linux

[Ulukai55]

Hello all,

I've been playing Brutal Doom Black Edition 3.1d for some weeks with several megawads on GZDoom 3.6.0 without problems. Running Arch Linux x64 with an AMD Radeon RX 580 and using the GZDoom version from the AUR. But since the update to GZDoom 3.7.0 and GZDoom 3.7.1 the game crashes every time, after a minute or so. I'm using a Doom launcher called Enyo-Doom and I'm using the same gzdoom.ini config and the same launch order (first the Doom 2 IWAD, then the megawad, then shared resources like lights, brightmaps and zd_extra, and then BDBE 3.1d). Starting with a different launch order or without a gzdoom.ini (so the default values are set again) doesn't help.

Replicate this by launching Doom (2) + megawad + BDBE and let the title map play. You'll see a turning camera, which after a round enters a pathway to fighting demons. At that point, the engine crashes, and I return to my desktop. Every time. Tried it with A Doom Odyssey and Scythe 2. Even quickly loading a game before the title map reaches the point of the fighting demons doesn't help. A couple of seconds after entering the level, the engine still crashes.

However...

• I can run Doom Slayer Chronicles with the same BDBE version just fine. With the one difference being that DSC has its own title map, not the default one from DSC and without fighting demons. Also DPWH-BE (a standalone mod using the underlying BDBE 3.1d) runs just fine. So my guess is maybe it has something to do with something in the title map?
• Running the same megawads with Brutal Doom v21 RC4 (not the Black Edition), also works without problems.
• I also tried reproducing it on Windows, with the same GZDoom and mod versions, but fail to do so. It seems everything still works on Windows, no crashes.

I have no idea how I can generate a GZDoom crash report, or where to find it, but I was able to let gzdoom write a log file using the autoexec parameters. It is attached to this report.
Please tell me if you need more information, and how I can gather it.

GZDoom Arch Linux: https://aur.archlinux.org/packages/gzdoom/
Enyo-Doom Arch Linux: https://aur.archlinux.org/packages/enyo-doom/
Brutal Doom Black Edition: https://www.moddb.com/addons/brutal-doo ... ck-edition
Don't Play With Hell Black Edition: https://www.moddb.com/mods/dont-play-wi ... gue-x64-13
Megawad A Doom Odyssey (Doom): https://www.doomworld.com/idgames/level ... s/2002ad10
Megawad Scythe 2 (Doom 2): https://www.doomworld.com/idgames/level ... ds/scythe2

[Rachael]

We have no control over Arch Linux's AUR, but I have a feeling I know who does. Have you tried our compile, instead? (You should remove your GZDoom 3.7.1 package first, so they don't conflict)

Your package manager should open automatically when you open our version.

If our version works, then you will have to let the maintainer know. (I *think* it is Grubber, he can be reached via PM on these forums) His compile may have gotten corrupted.

[Ulukai55]

Thanks for your reply.

No I didn't try another install source than AUR.
Do you mean to use the howto as listed here: https://zdoom.org/wiki/Compile_GZDoom_on_Linux?

[Marisa the Magician]

I see the crash here. I wonder if the couple dozen warnings about "Self pointer used in ambiguous context; VM execution may abort!" from the mod's zscript have anything to do with this.

[Rachael]

Thanks for your reply.

No I didn't try another install source than AUR.
Do you mean to use the howto as listed here: https://zdoom.org/wiki/Compile_GZDoom_on_Linux?

No, I mean this build - but if you feel comfortable compiling it on your own that works too.

[Ulukai55]

I see the crash here. I wonder if the couple dozen warnings about "Self pointer used in ambiguous context; VM execution may abort!" from the mod's zscript have anything to do with this.

You have the same crash?
I've seen the warnings in my log files as well, but can't really understand what's going on and whether they are the culprit. But the mod hasn't changed versions since I'm using it, and it worked fine this way with GZDoom 3.6.0.

[Ulukai55]

No, I mean this build - but if you feel comfortable compiling it on your own that works too.

Oh I see! Thanks!
I will give it a try tonight, I'm at work right now so no access to my gaming rig. Will update post after I tried and take action to get in touch with the AUR maintainer (you're right, it is Grubber) if that seems to be the problem.

[Rachael]

Well - keep in mind, it may not be a problem on his end, that's why I asked you to try our's, first. If you get the same problem with our's, then it is a code problem. I'm merely asking for a process of elimination.

[Marisa the Magician]

I'm going to see if I can get a trace on this. So far I've noticed that it doesn't happen with debug builds.

Edit: Hmmm... well, this is weird. Are you sure you're using 3.7.1 specifically? If I build that the crash doesn't happen.

Edit 2: Oh wait, maybe it's because of the specific config in the AUR package, since it uses the asmjit in the AUR, among other things.

[Rachael]

AFAIK that's not going to work because if I remember correctly, we had to make changes to asmjit. I am not 100% positive on that, though. If that's the case, CMake should be changed to not be looking for an external version of it.

[phantombeta]

Most definitely. The AsmJit in the AUR will be/is from the AsmJit repo, and that'll not work at all - we had to make changes to fix some quite serious register allocation bugs that were stopping progress.

[Rachael]

I will fix CMakeLists.txt later today to not use external ASMJit libraries, then.

[Rachael]

I will fix CMakeLists.txt later today to not use external ASMJit libraries, then.

And done. I will keep this open, though, until I get some sort of confirmation that the Arch Linux version has been recompiled without the external dependency.

[Ulukai55]

Wow, thanks for the quick investigation and changes.
I will try some things tonight and post back with the results.

[Ulukai55]

Like you suggested from the beginning, it works with the extracted bin from your Linux build. I posted a lonk on the air page to this thread to let the maintainer know about it.

Thanks a lot for all the help. Consider this solved!