mupen64plus-libretro-nx [GlideN64][Linux] Black screen after switching to fullscreen

When I play any game using the GlideN64 plugin and switch to fullscreen (or start in fullscreen and switch to windowed), the core's video output goes completely black and stays that way until I close the content. I can still hear the game's audio and open the RetroArch menu, and the game seems to be completely playable otherwise. This doesn't happen when I use Angrylion, and both plugins work fine on Windows. I've tried toggling exclusive fullscreen mode on/off, switching between gl, glcore, and vulkan as video drivers, and messing around with various core options, but nothing made a difference.

Mupen64Plus: 81a58df RetroArch: 9e25601 (1.8.4 stable) OS: Ubuntu 19.10 CPU: AMD Ryzen 5 3600 GPU: AMD Radeon RX 580 OpenGL: 4.5 (Compatibility Profile) Mesa 19.2.8

mupen64plus-169screensize = "1920x1080"
mupen64plus-43screensize = "1280x960"
mupen64plus-alt-map = "True"
mupen64plus-angrylion-multithread = "all threads"
mupen64plus-angrylion-overscan = "disabled"
mupen64plus-angrylion-sync = "Low"
mupen64plus-angrylion-vioverlay = "Filtered"
mupen64plus-aspect = "4:3"
mupen64plus-astick-deadzone = "5"
mupen64plus-astick-sensitivity = "100"
mupen64plus-BackgroundMode = "OnePiece"
mupen64plus-BilinearMode = "3point"
mupen64plus-CorrectTexrectCoords = "Off"
mupen64plus-CountPerOp = "0"
mupen64plus-cpucore = "dynamic_recompiler"
mupen64plus-d-cbutton = "C3"
mupen64plus-EnableCopyColorToRDRAM = "Async"
mupen64plus-EnableCopyDepthToRDRAM = "Software"
mupen64plus-EnableEnhancedHighResStorage = "False"
mupen64plus-EnableEnhancedTextureStorage = "False"
mupen64plus-EnableFBEmulation = "True"
mupen64plus-EnableFragmentDepthWrite = "True"
mupen64plus-EnableHWLighting = "False"
mupen64plus-EnableLegacyBlending = "False"
mupen64plus-EnableLODEmulation = "True"
mupen64plus-EnableN64DepthCompare = "False"
mupen64plus-EnableNativeResTexrects = "Disabled"
mupen64plus-EnableOverscan = "Enabled"
mupen64plus-EnableShadersStorage = "True"
mupen64plus-EnableTextureCache = "True"
mupen64plus-ForceDisableExtraMem = "False"
mupen64plus-FrameDuping = "False"
mupen64plus-Framerate = "Original"
mupen64plus-FXAA = "0"
mupen64plus-l-cbutton = "C2"
mupen64plus-MaxTxCacheSize = "8000"
mupen64plus-MultiSampling = "0"
mupen64plus-NoiseEmulation = "True"
mupen64plus-OverscanBottom = "0"
mupen64plus-OverscanLeft = "0"
mupen64plus-OverscanRight = "0"
mupen64plus-OverscanTop = "0"
mupen64plus-pak1 = "memory"
mupen64plus-pak2 = "none"
mupen64plus-pak3 = "none"
mupen64plus-pak4 = "none"
mupen64plus-r-cbutton = "C1"
mupen64plus-rdp-plugin = "gliden64"
mupen64plus-rsp-plugin = "hle"
mupen64plus-txCacheCompression = "True"
mupen64plus-txEnhancementMode = "None"
mupen64plus-txFilterIgnoreBG = "True"
mupen64plus-txFilterMode = "None"
mupen64plus-txHiresEnable = "False"
mupen64plus-txHiresFullAlphaChannel = "False"
mupen64plus-u-cbutton = "C4"
mupen64plus-virefresh = "Auto"

Mar 01 '20 07:03 d07434b2c08f

Can confirm this bug on my setup as well (system details in issue #161)

Mar 15 '20 00:03 gilmorem560

There was a bug in RetroArch a few weeks ago that would make widgets crash on context reset. Does it still happen with latest master? I have doubts there would be a linux only context reset issue.

Mar 18 '20 15:03 m4xw

I'll have to pull down master tonight and check, latest code I have currently is tag 1.8.4

Mar 18 '20 15:03 gilmorem560

So the core just straight up fails to load on the latest trunk, I don't get anything in the way of error feedback on stdout or stderr, so not sure what is going on there, but figured the feedback would be helpful. Additionally, I do get some console errors on 1.8.4, namely that the VAOs are no longer bound when going between fullscreen/windowed. Unsure if that is a symptom of the context being lost or literally that the VAOs are somehow getting destroyed/freed in the switching process, but hopefully that's at least some sort of lead as to what is going on. If nothing else I'll revisit this with 1.8.5 when it gets tagged. Verified that other cores I'm running aren't having loading issues on trunk though, so can at least rule out that trunk is broken completely.

Mar 19 '20 00:03 gilmorem560

What did you set as video driver in ra?

Mar 19 '20 13:03 m4xw

gl, I haven't tried glcore or gl1 but remember having trouble with those in the past in other regards. Vulkan fails for me although I haven't put a lot of effort into it, this machine is going by the wayside soon.

Mar 19 '20 15:03 gilmorem560

RetroArch 1.8.9 now, video driver is gl, on commit f68044f

Seems to just happen whenever going between the two, closing content and opening again brings video back. Not a show stopper just figured I'd give an update

Jun 23 '20 05:06 gilmorem560

This Bugs affects me too