Crashes on 5.0-15993

Lucbl1 · 02-11-2022, 11:40 PM #1

Hello. I've been using dolphin normally (with hybrid ubershaders mode, to cut on the stutters), but since updating it to the newest version, it crashes on anything besides Specialized mode. Is this a bug?

**JosJuice** · (This post was last modified: 02-12-2022, 12:02 AM by JosJuice.)

Yes, but it may be a bug in your graphics drivers rather than Dolphin. We're not entirely sure.

Lucbl1 · 02-11-2022, 11:58 PM #3

I see. Well I'm using a Galaxy Note 10+ on android 12. It's a Snapdragon 855.

Here are the driver Versions:

OpenGL Version: OpenGL ES 3.2 V@0502.0 (GIT@3dad7f8ed7, I593c16c433, 1633080534) (Date:10/01/21)

Vulkan Version: 1.1.128 (-2145427456)

Just as info, it didn't work on android 11 too.

Meanwhile I'll keep using the latest stable version before this one..

Lucbl1 · 02-12-2022, 12:19 AM #4

BTW, thanks for the quick answer and availability!

LeviathaninWaves · 02-13-2022, 11:35 AM #5

I'm also having frequent crashing issues on the same Dolphin revision. Unlike the poster above, I'm using specialized shaders.
I've tried both OpenGL and Vulkan. Dual Core and Sync on idle are both enabled.

The crashing seems to happen within the first 10-15 minutes of play. Twilight Princess and Wind Waker. They seem to occur most frequently while transitioning between areas but have also happened outside of this condition (may be no correlation).
Android 12, Note 20 Ultra, Snapdragon 865+, Adreno 650. Good luck, seems like they could be segmentation faults. I did get some invalid read popups, but not every crash.

**JosJuice** · 02-13-2022, 07:35 PM #6

(02-13-2022, 11:35 AM)LeviathaninWaves Wrote: I'm also having frequent crashing issues on the same Dolphin revision. Unlike the poster above, I'm using specialized shaders.
I've tried both OpenGL and Vulkan. Dual Core and Sync on idle are both enabled.

The crashing seems to happen within the first 10-15 minutes of play. Twilight Princess and Wind Waker. They seem to occur most frequently while transitioning between areas but have also happened outside of this condition (may be no correlation).
Android 12, Note 20 Ultra, Snapdragon 865+, Adreno 650. Good luck, seems like they could be segmentation faults. I did get some invalid read popups, but not every crash.

I think you're running into a different bug than the ubershader bug. Does this test build fix it? https://dl.dolphin-emu.org/prs/22/dc/pr-10447-dolphin-latest.apk

(Source code: https://github.com/dolphin-emu/dolphin/pull/10447)

Lucbl1 · 02-14-2022, 01:56 AM #7

(02-13-2022, 11:35 AM)LeviathaninWaves Wrote: I'm also having frequent crashing issues on the same Dolphin revision. Unlike the poster above, I'm using specialized shaders.
I've tried both OpenGL and Vulkan. Dual Core and Sync on idle are both enabled.

The crashing seems to happen within the first 10-15 minutes of play. Twilight Princess and Wind Waker. They seem to occur most frequently while transitioning between areas but have also happened outside of this condition (may be no correlation).
Android 12, Note 20 Ultra, Snapdragon 865+, Adreno 650. Good luck, seems like they could be segmentation faults. I did get some invalid read popups, but not every crash.

I was going to post the exact same thing. After I tested the MMJR2 fork and encountered the same crashes. Happens only after enabling dual core. Does this has something to do with PrimitiveRestart?

**JosJuice** · 02-14-2022, 02:09 AM #8

Lucbl1, I'm not sure if I follow. At first you said it crashes unless you used specialized mode, but now you said that you're having the same crashes as LeviathaninWaves, who is getting crashes even in specialized mode. Which one of the two is it?

I don't think this has anything to do with primitive restart either way.

Lucbl1 · 02-14-2022, 02:13 AM #9

It crashes with ubershaders on. So I tried without them (specialized), and got a different type of crash. The game seemed to work fine for a while (Metroid Prime 2) but then it'd give a message about the cpu and gpu getting desynced. After some seconds, it crashed.

So it's a different crash. Sorry I didn't make it clearer.

**JosJuice** · 02-14-2022, 02:20 AM **#10**

If you're getting a message about the GPU being desynced, that's most likely just the regular kind of dual core crash that's existed for ages. If you have Config > Advanced > Synchronize GPU Thread set to Never, please change it back to On Idle Skipping. Otherwise, your best bet is to simply disable dual core.