Emulator Issues #12327
JitArm64: Crash when loading games due to 5.0-13127
What's the problem? Describe what went wrong.
Attempt to load a game. Logcat produces nothing helpful here. Video backend OSD information never displays and screen remains black. App freezes when attempting to exit emulation.
What steps will reproduce the problem?
Play any game.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Is the issue present in the latest stable version?
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
What are your PC specifications? (CPU, GPU, Operating System, more)
Samsung Galaxy Note8 (SM-N950U)
Qualcomm Snapdragon 835
Octa-core (4x2.35 GHz Kryo & 4x1.9 GHz Kryo)
6GB RAM (LPDDR4)
OpenGL ES 3.2 V@331.0
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
I'll be unavailable to look into this issue further today.
#3 Updated by JosJuice about 2 months ago
Here's the culprit (which makes no sense to me at all): https://github.com/dolphin-emu/dolphin/commit/e00572dd07fc2b488805e0a28265eaaffb2a7bf2#diff-beb1004068233f1418f0514f91a2781175c93ab1268aa1d8ccd411880241c22bR597-R598
#6 Updated by ryanebola16 about 2 months ago
Something weird is going on here. Seemingly any
*_LOG_FMT message called in
CheckExceptions() triggers this problem, except for
DEBUG_LOG_FMT since I assume
#if defined(_DEBUG) == false in
Log.h when building the app with
[:app:assembleDebug]. And removing the string variables from the message didn't help anything.
I'll need to revisit this if I think of something else to try.
#10 Updated by JosJuice about 1 month ago
- Fixed in set to 5.0-13187
- Status changed from Fix pending to Fixed