Project

General

Profile

Actions

Emulator Issues #11088

open

Super Smash Bros. (VC) - Ridiculous RAM Usage

Added by autofire372 almost 6 years ago. Updated about 2 years ago.

Status:
Accepted
Priority:
Normal
Assignee:
-
% Done:

0%

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

Description

Game Name?

Super Smash Bros.

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

NALE01

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

5a456fe4a88e67eec2bdf895aaa59ae2

What's the problem? Describe what went wrong.

The game causes Dolphin to chew through RAM at a ridiculous rate: Less than a minute in and it gobbles up 5GB of my 8GB of RAM, grinding my PC to a screeching halt.

What steps will reproduce the problem?

  1. Launch Dolphin
  2. Launch Super Smash Bros. (preferably with Task Manager already open)
  3. Observe RAM usage skyrocketing

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

The issue persists as of 5.0-7263.

Is the issue present in the latest stable version?

No, this is not a problem in 5.0 stable.

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 seems to be 5.0-5757, though I'm not sure that makes sense.

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)

CPU: Intel Core i7-4770k@4.4 Ghz
GPU: NVIDIA GeForce GTX 970 w/ 4GB VRAM
OS: Windows 10

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

[Anything else here]


Files

ram_usage_running.PNG (18.9 KB) ram_usage_running.PNG Game Running ZephyrSurfer, 11/20/2021 06:49 PM
ram_usage_stopped.PNG (11.4 KB) ram_usage_stopped.PNG Game Stopped after it's eaten some RAM ZephyrSurfer, 11/20/2021 06:49 PM
Actions #1

Updated by JMC4789 almost 6 years ago

I think staying at 1x IR prevents this from happening? We're caching a lot of stuff with this game - this issue has popped up before.

Actions #2

Updated by autofire372 almost 6 years ago

JMC4789 wrote:

I think staying at 1x IR prevents this from happening? We're caching a lot of stuff with this game - this issue has popped up before.

Yeah. On closer inspection, EFB2RAM works around the issue, confirming this as a reoccurrence of issue 8450.

Actions #3

Updated by Helios almost 6 years ago

  • Status changed from New to Accepted
  • Regression changed from No to Yes

Updated by ZephyrSurfer over 2 years ago

Broken in 5.0-4412 -> https://dolphin-emu.org/download/dev/e63c33783049753784a24675bfa0792e54684fbd/

I have tested with default settings and it has a memory leak too. It just takes a while to eat the RAM for me.

Stopping the game would usually clear a bunch of RAM but this leak will keep the RAM usage high until both the GUI and game are killed.

Actions #5

Updated by JosJuice over 2 years ago

  • Milestone set to Current
  • Regression start set to 5.0-4412
Actions #6

Updated by JMC4789 over 2 years ago

  • Status changed from Accepted to Fix pending

A temporary work-around that doesn't lock things to 1x IR or greatly increase system requirements has been tested to work. While it's not a full solution to the problem, it should be fixed "good enough" for now.

Tested in PR10236 -> https://github.com/dolphin-emu/dolphin/pull/10236

Once that's merged, we should be able to remove the current tag on this.

Actions #7

Updated by JMC4789 about 2 years ago

  • Status changed from Fix pending to Accepted
  • Milestone deleted (Current)

Default settings prevent this issue from happening now.

Actions

Also available in: Atom PDF