Emulator Issues #11283
[JITARM] House Of The Dead Overkill Crashes
[Put Game Name here]
House Of The Dead Overkill
Game ID? (right click the game in the game list, properties, info tab)
[Put Game ID here]
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
[Put MD5 Hash here]
What's the problem? Describe what went wrong.
House Of The Dead Overkill only works when using Cached Interpreter,JITARM64 causes it to crash on startup
What steps will reproduce the problem?
Try starting House Of The Dead Overkill with JITARM64 enable,it will crash on startup....single core,dual core,gl/Vulkan no other setting matters once dolphin isn't set to use the cached interpreter..the game will crash
[Reproduction steps here]
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
[Version number here]
Is the issue present in the latest stable version?
[Yes/No and version number here]
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.)
[First broken version number here (if applicable)]
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]
What are your PC specifications? (CPU, GPU, Operating System, more)
NVIDIA SHIELD TV TEGRA X1
[PC specs here]
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
[Anything else here]
#1 Updated by JMC4789 about 2 years ago
While this issue report lacks a lot of crucial information I'd normally require, this issue sounds valid based on what you're writing. The question is how we go about debugging it. What we'd want to do normally is fallback various instructions to the interpreter until we find the one broken in the JIT, but, doing so in Android requires you to be able to compile.