RetroArch randomly freezes and dies when playing specific games

Is there an existing issue for this?

• This is a bug in RetroArch frontend
• I have searched the existing issues

Description

This is a weird one to explain, so please bear with me: while playing specific games on RetroArch, the whole program will basically freeze and die at random points. It's very consistent with at least one game, but I've experienced it in others. When the bug manifests it's very consistent in behaviour - the graphics die and the window stops responding visually to inputs, but the game keeps playing and can receive inputs (observable via sound, which keeps working normally).

This has only happened on Vulkan as far as I'm aware, so it could be something to do with that.

Games where it happens:

• Zelda II: The Adventure of Link (run through Mesen). This is the biggest culprit - sometimes it'll die on startup, sometimes as a game is loading, often when any sort of flicker happens (typically the ones at the end of palaces or when learning spells).
• Castlevania: Aria of Sorrow (run through mGBA). It only happened a handful of times here, but I remember them distinctly. I think it happened when I moved through a room?

I finally got video proof of it happening, it's here: https://youtu.be/R_smjPxMMkA

In the video I'm using the Flash Removal patch for Zelda II, but it's consistent across both the patched and unpatched versions, unfortunately.

I'm on Arch Linux, using the latest version of RetroArch and everything else as of writing (I made sure to update everything before recording the video, just in case). Happy to post specs as needed.

Expected behavior

RetroArch shouldn't freeze randomly.

Steps to reproduce the bug

1. Play on Linux. (Maybe relevant?)
2. Set graphics to Vulkan.
3. Launch Zelda II through Mesen and try to play normally.
4. Observe crashes.

Version/Commit

1.22.2

Bisect Results

No response

Present in the nightly version

I don't know

Platform & operating system

Arch Linux

Affected Cores

Mesen, mGBA (far rarer)

Environment information

Window manager: KWin, I think? Affected video drivers: Vulkan

Relevant log output

I've checked and nothing shows up in the log when this bug occurs. I can provide proof as needed.