Emulator

MayImilae wrote in #note-1:

Can you give us some screen recordings of these bugs please? You can use the built-in screenshot tool to record the screen, or something like OBS.

Please give us screenshots at the very least.

I will try to do that. It's a bit tricky since these artefacts are appearing and disappearing very quickly.

Yikes, web compositor bugs. So this is likely a macOS Intel Graphics driver issue from whatever Intel driver macOS has for you Intel HD Graphics 515 GPU, and that is then interacting badly with something in Chrome. Because there are multiple layers of things interacting with eachother to cause this, it's going to be an absolute pain to reproduce even for someone with the same hardware! It could be Chrome's fault for all we know. And worse yet, I don't know of anyone with that hardware in the project - the 12in MacBook was not exactly a popular gaming machine. Personally, I don't have an Intel Graphics 515 mac to test against, I have older (HD4000) and newer (Iris Plus Graphics 655)... which are 3 years older and 3 years newer, ironically.

EDIT: I've been told that that generation of Intel Graphics has known hardware bugs. Even more yikes.

So let's just start with basic troubleshooting. Does this happen on our OpenGL or Metal Graphics Backends?

MayImilae wrote in #note-4:

So let's just start with basic troubleshooting. Does this happen on our OpenGL or Metal Graphics Backends?

I tested this with the Vulkan render backend, which on Mac OS probably means that it's using Metal via MoltenVK, but I am not an expert on the specifics of the implementation. I could try if this is reproducible with the OpenGL and Metal backends as well.

I should maybe stress again, that this happens AFTER the Dolphin process was terminated, so the GPU seems to be in a compromised state at this point. I might be wrong, but applications should not be able to permanently change the state of the GPU after the respective process has ended, or should they? If not, then the fact that this is even possible would point toward a driver bug on Apple's side. There is probably still a way to not trigger this bug, though.

Update: I tried to reproduce the issue using the Metal renderer. This did not trigger the graphics artifacts described above, so it seems this is a Vulkan-only issue.