Project

General

Profile

Emulator Issues #12336

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

Added by v1993 5 months ago. Updated 5 months ago.

Status:
New
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.

History

#1 Updated by JMC4789 5 months ago

For this to happen, your NAND is likely in a corrupted state in the first place. Either by doing things in an order not possible on Wii, or due to Dolphin's ability to actually go over the limit in terms of block size if you install things via the Gamelist.

#2 Updated by Pikachu025 5 months ago

Even in a corrupt data state we should never straight up crash, so I'd say this is still valid regardless.

#3 Updated by v1993 5 months ago

How can I test if NAND is in corrupted state? Wii Menu doesn't seem to indicate any issues when booted up.

#4 Updated by JMC4789 5 months ago

Tools Menu should have a NAND check option in Dolphin's GUI.

The other thing is that this might be an ES_Launch, maybe we broke it again.

#5 Updated by v1993 5 months ago

NAND check from tool also indicates no issues detected. Just in case, this happens both in BT pass-through and emulated wiimote modes.

#6 Updated by v1993 5 months ago

Gah, NAND check from tools menu, of course. Sorry for possible confusion.

#7 Updated by Pikachu025 5 months ago

Can you try turning on MMU (Settings -> Advanced -> CPU Options -> Enable MMU) and see if it still crashes the emulator then?

#8 Updated by v1993 5 months ago

Turing MMU on doesn't seem to change anything about crash.

#9 Updated by leoetlino 5 months ago

I cannot reproduce the issue on master. Please turn off fastmem by setting "Fastmem" to False in Dolphin.ini and post a stack trace.

#10 Updated by v1993 5 months ago

Curiously, turning off "Fastmem" option fixes the crash entirely, checked both under GDB and in normal run.

#11 Updated by v1993 5 months ago

After toying around more, I was able to get one crash under fastmem off by watching all videos and getting in-game, but it happened outside of debugger. After trying to reproduce it, dolphin exited properly, thus saving movies state and not showing them at boot any more.

While immediate issue is fixed, I can keep digging in if there is an idea how to catch this bug: its original form is worked around by turning fastmem off and I'm not sure second crash is related.

Also available in: Atom PDF