ZDoom

Yup, no freezes now.

Pushed a fix for this.

Edit: ah crap. I probably chased ghosts there because some fatal errors were converted to "recoverable" errors. The real bug is most likely the "Could not allocate descriptor sets" line in your output. Now I'm guessing it will just keep writing that or something worse.

Edit 2: did another push which I think explains the real reason it hung after a second.

Thanks. Okay now I understand the error message a little better. It is saying the command buffer has become invalid because we updated the descriptor set.

I pushed a commit that adds a vk_debug_callstack cvar (default on) that will attempt to include the call stack for the warning/error location when vk_debug is enabled. If you run gzdoom in a debug build I believe that will write out the info I need on Linux.

If possible, it would help a lot if you could set a breakpoint in line 383 in vk_device.cpp (VulkanDevice::DebugCallback) - just before you type gl_bloom 1. Knowing the call stack for whatever is invalidating that command buffer might help getting closer to the source of this problem.

Try enable vk_debug and see if it generates any errors. With some luck they can give a hint what is going wrong.

Everything works fine until I try enabling any form of postprocessing, be it bloom, ssao, fxaa or anything else. Once I do, gzdoom freezes after a second.

Here's the vulkaninfo output from the laptop.