Freeze when loading rom

[alfredorusso-github]

When i try to load a rom, in my case Pokemon Heart Gold the emulator just freeze as you can see here:

I tried also with other roms and the problem is the same. I tried with other emulator and they haven't such a problem to load the rom. I need this emulator for the lua console.

I have installed mono as you can see in the following image:

There is no error inside the EmuHawkMono_laststderr.txt file.

Instead this is the output of the EmuHawkMono_laststdout.txt file:

stdout

``` Using OpenTK 3 for host input (keyboard + gamepads) Game was not in DB. CRC: FFD28F00 MD5: AE2A483D0A5E8130D39F44F41A86DF57 MemoryBlock created for address 36f00000000:36f41347000 with mirror 7f4a96cb8000:7f4ad7fff000 Mouting `melonDS.wbx` @36f00000000 Sections: @0:0 `` 0 bytes @36f000002a8:36f000002eb R `.interp` 67 bytes @36f000002ec:36f00000304 R `.note.gnu.build-id` 24 bytes @36f00001000:36f00001003 R X `.init` 3 bytes @36f00001010:36f001b7d3e R X `.text` 1797422 bytes @36f001b7d3e:36f001b7d41 R X `.fini` 3 bytes @36f001b8000:36f00281880 R `.rodata` 825472 bytes @36f00281880:36f00295944 R `.eh_frame_hdr` 82116 bytes @36f00295948:36f002fda64 R `.eh_frame` 426268 bytes @36f002fda64:36f00305314 R `.gcc_except_table` 30896 bytes @36f00306000:36f00306028 RW `.init_array` 40 bytes @36f00307000:36f004e0280 RW `.invis` 1938048 bytes @36f004e1000:36f004e1368 RW `.data` 872 bytes @36f004e1370:36f00b43fd8 RW `.bss` 6696040 bytes @36f00b44fd8:36f00b44fd8 RW `.ldata` 0 bytes @0:6f `.comment` 111 bytes @0:603a8 `.symtab` 394152 bytes @0:a8 `.shstrtab` 168 bytes @0:1c71bc `.strtab` 1864124 bytes Segments: %36f00000040:36f000002a8 R 616 bytes %36f000002a8:36f000002eb R 67 bytes %36f00000000:36f00000304 R 772 bytes %36f00001000:36f001b7d41 R X 1797441 bytes %36f001b8000:36f00305314 R 1364756 bytes %36f00306000:36f00306028 RW 40 bytes %36f00307000:36f00b44fd8 RW 8642520 bytes %36f00306000:36f00307000 R 4096 bytes %36f00281880:36f00295944 R 82116 bytes %36f000002ec:36f00000304 R 24 bytes Calling _start() Initializing heap sbrk at 36f00d45000:36f00f45000 Allocated 20480 bytes on sbrk heap, usage 20480/2097152 Allocated 69632 bytes on sbrk heap, usage 90112/2097152 Allocated 36864 bytes on sbrk heap, usage 126976/2097152 Allocated 12288 bytes on sbrk heap, usage 139264/2097152 Allocated 4096 bytes on sbrk heap, usage 143360/2097152 Allocated 4096 bytes on sbrk heap, usage 147456/2097152 Allocated 4096 bytes on sbrk heap, usage 151552/2097152 Allocated 4096 bytes on sbrk heap, usage 155648/2097152 Allocated 4096 bytes on sbrk heap, usage 159744/2097152 Allocated 4096 bytes on sbrk heap, usage 163840/2097152 Allocated 4096 bytes on sbrk heap, usage 167936/2097152 Allocated 4096 bytes on sbrk heap, usage 172032/2097152 Allocated 4096 bytes on sbrk heap, usage 176128/2097152 Allocated 4096 bytes on sbrk heap, usage 180224/2097152 Allocated 4096 bytes on sbrk heap, usage 184320/2097152 Allocated 4096 bytes on sbrk heap, usage 188416/2097152 Allocated 4096 bytes on sbrk heap, usage 192512/2097152 Allocated 4096 bytes on sbrk heap, usage 196608/2097152 Allocated 4096 bytes on sbrk heap, usage 200704/2097152 Allocated 4096 bytes on sbrk heap, usage 204800/2097152 Allocated 4096 bytes on sbrk heap, usage 208896/2097152 Allocated 4096 bytes on sbrk heap, usage 212992/2097152 Allocated 4096 bytes on sbrk heap, usage 217088/2097152 Allocated 4096 bytes on sbrk heap, usage 221184/2097152 Allocated 4096 bytes on sbrk heap, usage 225280/2097152 Allocated 4096 bytes on sbrk heap, usage 229376/2097152 Allocated 4096 bytes on sbrk heap, usage 233472/2097152 Allocated 4096 bytes on sbrk heap, usage 237568/2097152 Allocated 4096 bytes on sbrk heap, usage 241664/2097152 Allocated 4096 bytes on sbrk heap, usage 245760/2097152 Allocated 4096 bytes on sbrk heap, usage 249856/2097152 Allocated 4096 bytes on sbrk heap, usage 253952/2097152 Allocated 4096 bytes on sbrk heap, usage 258048/2097152 Allocated 4096 bytes on sbrk heap, usage 262144/2097152 Allocated 4096 bytes on sbrk heap, usage 266240/2097152 Allocated 4096 bytes on sbrk heap, usage 270336/2097152 Allocated 4096 bytes on sbrk heap, usage 274432/2097152 Allocated 4096 bytes on sbrk heap, usage 278528/2097152 Allocated 4096 bytes on sbrk heap, usage 282624/2097152 Allocated 4096 bytes on sbrk heap, usage 286720/2097152 Allocated 4096 bytes on sbrk heap, usage 290816/2097152 Allocated 4096 bytes on sbrk heap, usage 294912/2097152 Allocated 4096 bytes on sbrk heap, usage 299008/2097152 Allocated 4096 bytes on sbrk heap, usage 303104/2097152 Allocated 45056 bytes on sbrk heap, usage 348160/2097152 Allocated 4096 bytes on sbrk heap, usage 352256/2097152 Allocated 4096 bytes on sbrk heap, usage 356352/2097152 Allocated 4096 bytes on sbrk heap, usage 360448/2097152 Allocated 4096 bytes on sbrk heap, usage 364544/2097152 Allocated 4096 bytes on sbrk heap, usage 368640/2097152 Allocated 4096 bytes on sbrk heap, usage 372736/2097152 Allocated 4096 bytes on sbrk heap, usage 376832/2097152 Allocated 4096 bytes on sbrk heap, usage 380928/2097152 Allocated 4096 bytes on sbrk heap, usage 385024/2097152 Allocated 4096 bytes on sbrk heap, usage 389120/2097152 Allocated 4096 bytes on sbrk heap, usage 393216/2097152 Allocated 4096 bytes on sbrk heap, usage 397312/2097152 Allocated 4096 bytes on sbrk heap, usage 401408/2097152 Allocated 4096 bytes on sbrk heap, usage 405504/2097152 Allocated 4096 bytes on sbrk heap, usage 409600/2097152 Allocated 4096 bytes on sbrk heap, usage 413696/2097152 Allocated 4096 bytes on sbrk heap, usage 417792/2097152 Allocated 4096 bytes on sbrk heap, usage 421888/2097152 Allocated 4096 bytes on sbrk heap, usage 425984/2097152 Allocated 4096 bytes on sbrk heap, usage 430080/2097152 Allocated 4096 bytes on sbrk heap, usage 434176/2097152 Allocated 4096 bytes on sbrk heap, usage 438272/2097152 Allocated 4096 bytes on sbrk heap, usage 442368/2097152 Allocated 4096 bytes on sbrk heap, usage 446464/2097152 Allocated 4096 bytes on sbrk heap, usage 450560/2097152 Allocated 4096 bytes on sbrk heap, usage 454656/2097152 Allocated 4096 bytes on sbrk heap, usage 458752/2097152 Allocated 4096 bytes on sbrk heap, usage 462848/2097152 Allocated 4096 bytes on sbrk heap, usage 466944/2097152 Allocated 4096 bytes on sbrk heap, usage 471040/2097152 Allocated 4096 bytes on sbrk heap, usage 475136/2097152 Allocated 4096 bytes on sbrk heap, usage 479232/2097152 Allocated 4096 bytes on sbrk heap, usage 483328/2097152 Allocated 4096 bytes on sbrk heap, usage 487424/2097152 Allocated 4096 bytes on sbrk heap, usage 491520/2097152 Allocated 4096 bytes on sbrk heap, usage 495616/2097152 Allocated 4096 bytes on sbrk heap, usage 499712/2097152 Allocated 4096 bytes on sbrk heap, usage 503808/2097152 Allocated 4096 bytes on sbrk heap, usage 507904/2097152 Allocated 4096 bytes on sbrk heap, usage 512000/2097152 Allocated 4096 bytes on sbrk heap, usage 516096/2097152 Allocated 4096 bytes on sbrk heap, usage 520192/2097152 Allocated 4096 bytes on sbrk heap, usage 524288/2097152 Allocated 4096 bytes on sbrk heap, usage 528384/2097152 Allocated 4096 bytes on sbrk heap, usage 532480/2097152 Allocated 4096 bytes on sbrk heap, usage 536576/2097152 Allocated 4096 bytes on sbrk heap, usage 540672/2097152 Allocated 4096 bytes on sbrk heap, usage 544768/2097152 Allocated 4096 bytes on sbrk heap, usage 548864/2097152 Allocated 4096 bytes on sbrk heap, usage 552960/2097152 Allocated 4096 bytes on sbrk heap, usage 557056/2097152 Allocated 4096 bytes on sbrk heap, usage 561152/2097152 Allocated 4096 bytes on sbrk heap, usage 565248/2097152 Allocated 4096 bytes on sbrk heap, usage 569344/2097152 Allocated 4096 bytes on sbrk heap, usage 573440/2097152 Allocated 4096 bytes on sbrk heap, usage 577536/2097152 Allocated 4096 bytes on sbrk heap, usage 581632/2097152 Allocated 4096 bytes on sbrk heap, usage 585728/2097152 Allocated 4096 bytes on sbrk heap, usage 589824/2097152 Initializing heap invisible at 0x36f00f46000:0x36f01346000 Allocated 196608 bytes on invisible heap, usage 196608/4194304 Allocated 196608 bytes on invisible heap, usage 393216/4194304 Allocated 196608 bytes on invisible heap, usage 589824/4194304 Allocated 196608 bytes on invisible heap, usage 786432/4194304 Allocated 135168 bytes on sbrk heap, usage 724992/2097152 MAC: 00:09:BF:0E:49:16 FW: WIFI CRC16 = GOOD FW: AP1 CRC16 = GOOD FW: AP2 CRC16 = GOOD FW: AP3 CRC16 = GOOD FW: USER0 CRC16 = GOOD FW: USER1 CRC16 = BAD Game code: IPKE ROM entry: 08000000 00000006 Cart ID: 00007FC2 Re-encrypting cart secure area Secure area decryption OK PU: region 0 = 04000033 : enabled, 04000000-08000000 PU: region 0 = 04000033 : enabled, 04000000-08000000 PU: region 1 = 0200002B : enabled, 02000000-02400000 PU: region 1 = 0200002B : enabled, 02000000-02400000 PU: region 2 = 00000000 : disabled, 00000000-00000002 PU: region 2 = 00000000 : disabled, 00000000-00000002 PU: region 3 = 08000035 : enabled, 08000000-10000000 PU: region 3 = 08000035 : enabled, 08000000-10000000 PU: region 4 = 0300001B : enabled, 03000000-03004000 PU: region 4 = 0300001B : enabled, 03000000-03004000 PU: region 5 = 00000000 : disabled, 00000000-00000002 PU: region 5 = 00000000 : disabled, 00000000-00000002 PU: region 6 = FFFF001D : enabled, FFFF0000-FFFF8000 PU: region 6 = FFFF001D : enabled, FFFF0000-FFFF8000 PU: region 7 = 027FF017 : enabled, 027FF000-02800000 PU: region 7 = 027FF017 : enabled, 027FF000-02800000 Game is now booting Calling ecl_seal() WaterboxHost Sealed! Setting up waterbox thread for 0x0000036F001B54F0 PU: region 0 = 04000033 : enabled, 04000000-08000000 PU: region 1 = 0200002D : enabled, 02000000-02800000 PU: region 2 = 027E0021 : enabled, 027E0000-02800000 PU: region 3 = 08000035 : enabled, 08000000-10000000 PU: region 4 = 027E001B : enabled, 027E0000-027E4000 PU: region 5 = 0100002F : enabled, 01000000-02000000 PU: region 6 = FFFF001D : enabled, FFFF0000-FFFF8000 PU: region 7 = 027FF017 : enabled, 027FF000-02800000 PU region 0: 04000000-08000000, user=00 priv=07 15111011/05100011 PU region 1: 02000000-02800000, user=70 priv=77 15111011/05100011 PU region 2: 027E0000-02800000, user=00 priv=00 15111011/05100011 PU region 3: 08000000-10000000, user=00 priv=03 15111011/05100011 PU region 4: 027E0000-027E4000, user=00 priv=03 15111011/05100011 PU region 5: 01000000-02000000, user=00 priv=07 15111011/05100011 PU region 6: FFFF0000-FFFF8000, user=50 priv=55 15111011/05100011 PU region 7: 027FF000-02800000, user=00 priv=03 15111011/05100011 ```

Hope you can help me.

[CasualPokePlayer]

Is this BizHawk 2.9.1?

Is this only for MelonDS or do other cores suffer the same issue? (e.g. are NES, GB, etc games fine)

If it's MelonDS only, can you try going to Config -> Core Settings -> For Handhelds -> MelonDS -> Settings -> Sync Settings and Set Threaded 3D Rendering to false?

[alfredorusso-github]

Yes it is BizHawk 2.9.1 and only MelonDS have this issue, I tried also gba and it works. Anyway I tried your solution but nothing changed.

[YoshiRulz]

Can you try one of the SNES, Genesis, or Saturn cores, or the default PSX core Nymashock?

[alfredorusso-github]

I downloded all the firmware and try to run a psx game and it starts without problem. By the way I forgot to specify that I am on linux.

[EddieRingle]

I started experiencing these hangs as well. I believe I've narrowed it down to a recent Mesa update (23.0.3 -> 23.1.1 on Arch Linux) or otherwise something in the display stack, as it works again if I force Mesa to use software rendering instead of RadeonSI (run EmuHawk with LIBGL_ALWAYS_SOFTWARE=true). Mesa 23.1.2 is in the Arch testing repos, so at some point I might try to see if that resolves the issue.

I'll add that directly running melonDS 0.9.5 from the Arch repos works flawlessly. An interesting difference there is that melonDS opens a native Wayland window, whereas EmuHawk is still using X11/Xwayland.

[CasualPokePlayer]

Cores don't handle opening up windows or such, the frontend does it, so comparing melonDS's qt frontend to EmuHawk is comparing apples with oranges, only the emulation core (what just does the actual emulation) is the same.

If anything, if this is the same hang as the OP and as such only seems to be in the melonDS core, this is maybe related to the screen position filters (vertical vs horizontal, swapped screens, rotation), which are placed more on the frontend here, not the core (even then, don't think we do anything particularly special or wrong here, I'd think it may just be a GPU driver bug if anything).

[EddieRingle]

Cores don't handle opening up windows or such, the frontend does it, so comparing melonDS's qt frontend to EmuHawk is comparing apples with oranges, only the emulation core (what just does the actual emulation) is the same.

It's not just about what's opening the window, but how the OpenGL context and underlying buffers are created and communicated to the display server; depending on the setup those apples and oranges could be more alike than you might think. At any rate, it was a quick note as another potential avenue to look into. It's easy to test that as well, and it turns out melonDS with an X11/Xwayland window runs just as well as through Wayland directly, so that's probably ruled out, as you said.

this is maybe related to the screen position filters (vertical vs horizontal, swapped screens, rotation)

This seems like it might be it, actually. If the screen layout in the core settings is either Vertical or Horizontal when a ROM is loaded, the UI hangs. If it's set to just the top or bottom screen, the ROM loads fine, and once loaded the layout can even be switched back to Vertical or Horizontal without any immediate issues from what I can tell.

[CasualPokePlayer]

To be clear too, the core quite literally has no access to the GPU here (for us it's in a sort of sandboxed state so it couldn't do it if it tried to do it). The screen filtering stuff is in the frontend here, done entirely with custom code by us with an entirely different display stack, so not much actually in common with melonDS qt.

That said, the fact it only occurs with Vertical or Horizontal when the rom is loaded seems odd. The main difference between those and Top/Bottom is there are simply two draws instead one, for each subrectange (basic rundown is set sampler texture uniform -> set projection and model view uniforms -> bind vertices -> draw arrays, all those steps done twice instead of once here). And even if that was somehow an issue it wouldn't make sense that it could be switched back into?

[EddieRingle]

One more update, newer versions of Mesa (23.1.2 and 23.2.0-git) did not resolve the issue. However, I ran EmuHawk in a Weston compositor instance and it was able to load a ROM successfully, so perhaps it's a bug in KDE/KWin.

[YoshiRulz]

No problems here with KWin 5.25.5.

[EddieRingle]

Arch currently packages KWin ~5.25.5-2~ 5.27.5-2, and there are at least a handful of other packages that KDE spreads relevant functionality across. Based on the OP's screenshots, including the Mono build date, they're also running Arch/KDE like myself. I'm assuming you're on Manjaro, so you're likely still using the older releases that don't include the bug. It does look like Manjaro has various updates as of today, in fact, so perhaps you'll hit the issue after you update.

EDIT: Late night, typo'd KWin version

[YoshiRulz]

Plasma packages installed on my machine

``` $> for p in $(yay -Sg plasma | awk '{ print $2 }'); do yay -Ss $p | fgrep Installed; done extra/bluedevil 1:5.26.5-1 (475.8 KiB 1.7 MiB) [plasma] (Installed: 1:5.25.5-1) extra/breeze-icons 5.103.0-1 (6.7 MiB 71.3 MiB) [kf5] (Installed: 5.98.0-1) extra/breeze 5.26.5-1 (45.3 MiB 51.2 MiB) [plasma] (Installed: 5.25.5-1) extra/libndp 1.8-1 (19.2 KiB 56.7 KiB) (Installed) extra/kdsoap-ws-discovery-client git20200927-2 (281.0 KiB 956.9 KiB) (Installed) extra/gssdp 1.6.2-1 (59.4 KiB 250.4 KiB) (Installed: 1.4.0.1-1) extra/avahi 0.8+22+gfd482a7-3 (433.7 KiB 1.9 MiB) (Installed) extra/kactivitymanagerd 5.26.5-1 (178.9 KiB 713.7 KiB) [plasma] (Installed: 5.25.5-1) extra/kde-cli-tools 5.26.5-1 (942.8 KiB 4.1 MiB) [plasma] (Installed: 5.25.5-1) extra/kdecoration 5.26.5-1 (78.4 KiB 297.3 KiB) [plasma] (Installed: 5.25.5-1) extra/kdeplasma-addons 5.26.5-1 (1.0 MiB 5.4 MiB) [plasma] (Installed: 5.25.5-1) extra/kmenuedit 5.26.5-1 (1.0 MiB 1.8 MiB) [plasma] (Installed: 5.25.5-1) extra/libkscreen 5.26.5-1 (362.9 KiB 1.0 MiB) [plasma] (Installed: 5.25.5-1) extra/kscreenlocker 5.26.5-1 (190.6 KiB 752.3 KiB) [plasma] (Installed: 5.25.5-1) extra/kscreenlocker 5.26.5-1 (190.6 KiB 752.3 KiB) [plasma] (Installed: 5.25.5-1) extra/ksshaskpass 5.26.5-1 (29.2 KiB 96.8 KiB) [plasma] (Installed: 5.25.5-1) extra/ksystemstats 5.26.5-1 (183.8 KiB 975.6 KiB) [plasma] (Installed: 5.25.5-1) extra/kwayland-integration 5.26.5-1 (35.7 KiB 136.3 KiB) [plasma] (Installed: 5.25.5-2) extra/kwindowsystem 5.103.0-1 (837.2 KiB 1.9 MiB) [kf5] (Installed: 5.98.0-1) extra/kwin 5.26.5-2 (8.4 MiB 30.2 MiB) [plasma] (Installed: 5.25.5-2) extra/layer-shell-qt 5.26.5-1 (21.6 KiB 77.3 KiB) [plasma] (Installed: 5.25.5-2) extra/libkscreen 5.26.5-1 (362.9 KiB 1.0 MiB) [plasma] (Installed: 5.25.5-1) extra/libksysguard 5.26.5-1 (1.1 MiB 6.7 MiB) [plasma] (Installed: 5.25.5-1) extra/milou 5.26.5-1 (74.5 KiB 271.9 KiB) [plasma] (Installed: 5.25.5-1) extra/oxygen-sounds 5.26.5-1 (1.8 MiB 2.0 MiB) [plasma] (Installed: 5.25.5-1) extra/oxygen-sounds 5.26.5-1 (1.8 MiB 2.0 MiB) [plasma] (Installed: 5.25.5-1) extra/plasma-desktop 5.26.5-1 (7.6 MiB 23.0 MiB) [plasma] (Installed: 5.25.5-1) extra/plasma-integration 5.26.5-1 (159.5 KiB 545.5 KiB) [plasma] (Installed: 5.25.5-2) extra/plasma-nm 5.26.5-1.1 (1.9 MiB 9.4 MiB) [plasma] (Installed: 5.25.5-1) extra/plasma-systemmonitor 5.26.5-1 (235.2 KiB 1.1 MiB) [plasma] (Installed: 5.25.5-1) extra/plasma-workspace-wallpapers 5.26.5-1 (80.8 MiB 81.9 MiB) [plasma] (Installed: 5.25.5-1) extra/plasma-workspace 5.26.5-3 (19.0 MiB 47.7 MiB) [plasma] (Installed: 5.25.5-4) extra/plasma-workspace-wallpapers 5.26.5-1 (80.8 MiB 81.9 MiB) [plasma] (Installed: 5.25.5-1) extra/polkit-kde-agent 5.26.5-1 (65.0 KiB 253.7 KiB) [plasma] (Installed: 5.25.5-1) extra/powerdevil 5.26.5-1 (897.9 KiB 3.0 MiB) [plasma] (Installed: 5.25.5-1) extra/sddm-kcm 5.26.5-1 (111.9 KiB 456.5 KiB) [plasma] (Installed: 5.25.5-1) extra/systemsettings 5.26.5-1 (358.3 KiB 1.2 MiB) [plasma] (Installed: 5.25.5-1) extra/xdg-desktop-portal-kde 5.26.5-1 (227.2 KiB 810.7 KiB) [plasma] (Installed: 5.25.5-1) ```

[EddieRingle]

Likewise, on my machine:

``` λ for p in $(yay -Qg plasma | awk '{ print $2 }'); do yay -Q $p; done bluedevil 1:5.27.5-1 breeze 5.27.5-1 breeze-gtk 5.27.5-1 discover 5.27.5-1 drkonqi 5.27.5-1 flatpak-kcm 5.27.5-1 kactivitymanagerd 5.27.5-1 kde-cli-tools 5.27.5.1-1 kde-gtk-config 5.27.5-1 kdecoration 5.27.5-1 kdeplasma-addons 5.27.5-1 kgamma5 5.27.5-1 khotkeys 5.27.5-1 kinfocenter 5.27.5-1 kmenuedit 5.27.5-1 kpipewire 5.27.5-1 kscreen 5.27.5-1 kscreenlocker 5.27.5-1 ksshaskpass 5.27.5-1 ksystemstats 5.27.5-1 kwallet-pam 5.27.5-1 kwayland-integration 5.27.5-1 kwin 5.27.5-2 kwrited 5.27.5-1 layer-shell-qt 5.27.5-1 libkscreen 5.27.5-1 libksysguard 5.27.5-1 milou 5.27.5-1 oxygen 5.27.5-1 oxygen-sounds 5.27.5-1 plasma-browser-integration 5.27.5-1 plasma-desktop 5.27.5-1 plasma-disks 5.27.5-1 plasma-firewall 5.27.5-1 plasma-integration 5.27.5-1 plasma-nm 5.27.5-1 plasma-pa 5.27.5-1 plasma-systemmonitor 5.27.5-1 plasma-thunderbolt 5.27.5-1 plasma-vault 5.27.5-1 plasma-welcome 5.27.5-1 plasma-workspace 5.27.5-1 plasma-workspace-wallpapers 5.27.5-1 polkit-kde-agent 5.27.5-1 powerdevil 5.27.5-3 sddm-kcm 5.27.5-1 systemsettings 5.27.5-1 xdg-desktop-portal-kde 5.27.5-1 ```

(Sorry, I typo'd Arch's KWin version last night.) It does seem that Arch is a few releases ahead of Manjaro at the moment, so it would appear that there's either a new bug in KDE, or they fixed something that exposed a bug in EmuHawk or one of its dependencies (but given that it works in Weston and another wlroots-based compositor I tested, I'm leaning towards it being a KDE issue).

[EddieRingle]

@YoshiRulz Would you mind checking if you're able to reproduce the issue now? It looks like Manjaro is now on KWin 5.27.6, aligning it with Arch, which is still exhibiting this issue.

[YoshiRulz]

I won't be able to test on Manjaro for a while, but I'll revisit this with the other distro-specific issues.

[CasualPokePlayer]

A lot changed with melonDS with recentish commits, does this issue still occur on the latest dev build?

[monstro1]

I'm getting a similar issue when trying to run ps1 games, on the latest version of manjaro

[YoshiRulz]

OP's issue was with melonDS and explicitly not Nymashock. Can you open a new issue with more detail?