Project

General

Profile

Actions

Emulator Issues #10112

closed

The Simpsons Hit & Run: emulator crash before getting to the main menu since Dolphin 5.0-2070

Added by aldelaro5 about 8 years ago. Updated about 8 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:
5.0-2673

Description

Game Name?

The Simpsons Hit & Run

Game ID? (right click the game in the game list, properties, info tab)

GHQE7D

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

1e40a2405da61fa5ea7f2487a99439ea

What's the problem? Describe what went wrong.

Since Dolphin 5.0-2070 ( https://dolphin-emu.org/download/dev/8d0ce8ea478c46ad11fe302a07a4eaf2a205cb1a/ ), this game makes the emulator crash on me just before getting to the main menu a bit after the tittle screen. This version was found after a git bisect, particularly, this commit seems to have introduced the crash:

https://github.com/dolphin-emu/dolphin/pull/4716/commits/70caf447b9245fa966b066af1e5424887dd5b3b5

What steps will reproduce the problem?

  1. Start the game using Dolphin 5.0-2070 or newer
  2. On the press start prompt, press start, a cutscene with a sky should start, press A to skip it
  3. the emulator should crash after the fade out

Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?

Beside all the versions I went through using git bisect, I tested this on Dolphin 5.0-2577 which is where I first noticed the issue. I then checked out Dolphin 5.0-2002 to test if it was a regression and the crash didn't occured on this revision confirming it would be a regression, that's when I did the git bisect.

What are your PC specifications? (CPU, GPU, Operating System, more)

Arch Linux
Intel core i5 4690 3.5 Ghz
Intel HD Graphics 4600 (using Mesa 17)
8Gb RAM

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

I tried with and without MMU, didn't changed anything. Logs aren't really helpfull, they only mention disc reads and even GDB wasn't helpfull when it would crash, not even the call stack seems to help here. I also tried with and without debug mode, doesn't do anything.

Actions #1

Updated by degasus about 8 years ago

  • Status changed from New to Accepted
  • Assignee set to degasus
Actions #2

Updated by degasus about 8 years ago

  • Status changed from Accepted to Fixed

Fixed in 5.0-2673

Actions #3

Updated by JosJuice about 8 years ago

  • Fixed in set to 5.0-2673
Actions

Also available in: Atom PDF