Project

General

Profile

Emulator Issues #12327

JitArm64: Crash when loading games due to 5.0-13127

Added by ryanebola16 about 1 year ago. Updated 12 months ago.

Status:
Fixed
Priority:
High
Assignee:
% Done:

0%

Operating system:
Android
Issue type:
Bug
Milestone:
Current
Regression:
Yes
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
5.0-13127
Fixed in:
5.0-13187

Description

Game Name?

Any

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.

Yes, 5.0-13136

Is the issue present in the latest stable version?

No, 5.0.

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.)

https://dolphin-emu.org/download/dev/e00572dd07fc2b488805e0a28265eaaffb2a7bf2/

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)
Adreno 540
6GB RAM (LPDDR4)
Android 9
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.

History

#1 Updated by JosJuice about 1 year ago

  • Status changed from New to Accepted

Reproduced.

#2 Updated by JosJuice about 1 year ago

Reverting the changes to Source/Core/Core/PowerPC/PowerPC.cpp fixes it. It's not actually a crash, it's the CPU thread getting stuck somehow.

#4 Updated by JosJuice about 1 year ago

  • Assignee changed from Lioncash to JosJuice
  • Subject changed from Android: Crash when loading games due to 5.0-13127 to JitArm64: Crash when loading games due to 5.0-13127

#5 Updated by JosJuice about 1 year ago

Even though removing that one line fixes the problem, the line never actually seems to execute???

#6 Updated by ryanebola16 about 1 year ago

Something weird is going on here. Seemingly any *_LOG_FMT message called in CheckExternalExceptions or 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.

#7 Updated by JosJuice about 1 year ago

The issue happens when bcx calls WriteExceptionExit (which then calls CheckExceptions which then calls CheckExternalExceptions). Or at least it does in the case I'm testing, which is PAL Wii Play.

#8 Updated by JosJuice about 1 year ago

I give up for now. Have a hotfix: https://github.com/dolphin-emu/dolphin/pull/9296

#9 Updated by JosJuice about 1 year ago

  • Status changed from Accepted to Fix pending

#10 Updated by JosJuice 12 months ago

  • Fixed in set to 5.0-13187
  • Status changed from Fix pending to Fixed

Also available in: Atom PDF