You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Built .so with no problems -- using cmake from upstream easyrpg Date: Sat Apr 29 13:53:44 2023 -0600
On aarch64, debian sid, Xorg 1:7.7+23, Uptodate Mesa-Panfrost drivers
Alt-tabbing away from a game running in this core results in retroarch/core hanging and retroarch becoming unresponsive. Retroarch process doesn't respond to SIGINT anymore, needs kill -1 (SIGHUP)
Hang doesn't happen with other cores tested (bsnes, snes9x, picodrive).
Hang doesn't happen with standalone EasyRPG player - only the retroarch core.
Hang happens regardless of whether compositor is enabled or not (but do test it without compositor to force application to handle damage / redraws)
Hang also doesn't happen when the retroarch menu is brought-up before alt-tabbing away from the window.
Thanks so much for the work porting to retroarch! RPGMaker is so much nicer with a shader stack like xbrz + pi-crt! Thank you!
The text was updated successfully, but these errors were encountered:
Update: removing ~/config/retroarch/retroarch.cfg and letting retroarch generate a new clean .cfg file, then starting game from 'desktop launcher', I can not recreate the hangup.
Alt-tab away from game window and back now works without hanging.
I was using the minimal retroarch interface and shaders.
I will try to identify what custom config led to the hang.
Built .so with no problems -- using cmake from upstream easyrpg Date: Sat Apr 29 13:53:44 2023 -0600
On aarch64, debian sid, Xorg 1:7.7+23, Uptodate Mesa-Panfrost drivers
Alt-tabbing away from a game running in this core results in retroarch/core hanging and retroarch becoming unresponsive. Retroarch process doesn't respond to SIGINT anymore, needs kill -1 (SIGHUP)
Thanks so much for the work porting to retroarch! RPGMaker is so much nicer with a shader stack like xbrz + pi-crt! Thank you!
The text was updated successfully, but these errors were encountered: