Project

General

Profile

Actions

Emulator Issues #12336

closed

Segfault when stopping after watching MPlus intro movie in Wii Sports Resort

Added by v1993 almost 4 years ago. Updated over 3 years ago.

Status:
Invalid
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:

Description

Game Name?

Wii Sports Resort

Game ID? (right click the game in the game list, Properties, Info tab)

RZTE01

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

73e15e793056a13d973aee85f2259e32 (WBFS dump)

What's the problem? Describe what went wrong.

Original issue was that Wii MPlus intro movie started showing up out of nowhere despite playing a game before and save working properly.

However, this lead to discovery of another issue: dolphin crashed when exiting that game. After some research, it seems that it's intro movie that causes crash (segfault, to be exact).

What steps will reproduce the problem?

  1. Run Wii Sports Resort and make sure that it shows you Motion Plus intro movie (clear NAND, I think? this happens to me on every launch, however...)

  2. Press A on wiimote to start the series of movies
    This will promptly write Core/HW/EXI/EXI_DeviceIPL.cpp:308 N[OSREPORT]: << RVL_MWM - ACTIMAGINE_MO release build: Mar 26 2009 16:23:26 (0x4302_145) >> to console.

  3. Wait until second movie of the series begins. At this point, above string will be dumped into console once again.

  4. Stop dolphin using stop button, and...

Core/IOS/STM/STM.cpp:26 N[IOS_STM]: IOCTL_STM_IDLE or IOCTL_STM_SHUTDOWN received, shutting down
Segmentation fault (core dumped)

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

5.0-13138 (Revision: a34823df61df65168aa40ef5e82e44defd4a0138)

Is the issue present in the latest stable version?

Not tested

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

Not tested

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

Not a graphical issue

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

KUbuntu 20.10

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

If crash can't be reproduced by others, I would be more than glad to provide a stack trace. However, it seems that Dolphin intentionally triggers out-of-bounds memory access in JIT that it handles itself? This makes getting far enough to get to required backtrace tricky it seems.

Haven't tested non-jit backends for presence of crash yet.

Actions

Also available in: Atom PDF