Emulator Issues #12636

Aging Test report

Added by FireNX70 3 months ago. Updated 10 days ago.

% Done:


Operating system:
Issue type:
Relates to usability:
Relates to performance:
Relates to maintainability:
Regression start:
Fixed in:


Game Name?

Aging Test For Production Discs

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


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


What's the problem? Describe what went wrong.

There's two problems, at the very least. Probably a lot more.

  1. The test always reports the disc drive as being inoperative. This seems to be harmless.
  2. The first test crashes dolphin. It used to just hang on older versions. On newer versions it complains about an unknown pointer and as soon as you exit the dialog it shuts down. The values of the pointer, the program counter and LR (link register?) (0x03358f20, 0x80018800 and 0x80018c0c; respectively) seem to be consistent. A fourth value, r-time, provided by the test and printed below version date; also seems to consistently be 624 microseconds.

What steps will reproduce the problem?

Boot the game up, wait until the ARAM test is done (about 8s if running full speed) and press B. No other input seems to have any effect at this stage. The test suite later lists its button mappings, but it doesn't seem to respond to them before the crash happens.

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

Yes, 5.0-14988.

Is the issue present in the latest stable version?

Most likely. However, the test might not even boot on 5.0.

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 and anyone who is building Dolphin on their own can use git bisect.)

It's probably been broken from the very beginning, in some form or another.

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:


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


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

As a side note, the aging test started booting before 5.0-756. I can't go back any further than that without deleting my settings which I don't wanna bother with. It might have actually started booting before 540 though, since the wiki is already wrong about memcards having anything to do with the program's behavior (did the exact same thing both with and without memcards and always got the same results).

The only reason I decided to test this was to see if the recent DSP fixes did anything, which does not seem to be the case (sadly, the service disc's DSP tests don't seem to be affected either). Anyway, I'll bisect the hang's behavior change later.


#1 Updated by FireNX70 3 months ago

By the way, I just saw The behavior I observed was already there before any of the recent DSP commits were merged. I've tested with a build somewhere in the 13000s and it still crashed and spat the same values. I've also tested with the DSPLLE interpreter on 14988 and it behaves exactly the same as the recompiler.

#2 Updated by FireNX70 3 months ago

>=12548         Complains about drive, passes DI test, crash on DOL-FAT at 624 usec.
12436 - 12546   Complains about drive, passes DI test, crash on DOL-FAT at 324 usec.
11476 - 12426   Complains about drive, CMD ERR, not sure if during DI test or during DOL-FAT.
10497 - 11458   Complains about drive, passes DI test, crash on DOL-FAT at 324 usec.
<=10495         Complains about drive, passes DI test, hangs on DOL-FAT at 324 usec.

Worth noting is the fact that 11476 through 12426 don't crash or hang automatically, allowing the user to run some tests. That is, if the user can make heads or tails of the control scheme, which changes depending on where the cursor is. The timing change on the hang comes down to DI timing changes and the pointer, PC and LR values seem to be unaffected.

While testing some builds that didn't crash I ran a couple of DI tests. Some complained about command errors, some seemed to pass. IIRC, some EXI test crashed. Also, running the DOL-FAT test manually seems to crash the test suite too.

#3 Updated by FireNX70 3 months ago

Just to clarify, when testing on 11476 - 12426 the EXI test and DOL-FAT would hang, but Dolphin itself was fine.

#4 Updated by FireNX70 about 2 months ago

I recorded the test running on console around the same time I first posted this, but I only got around to uploading it now. Don't know if it'll help but here it is:

#5 Updated by ZephyrSurfer 10 days ago

In my testing the wiki is correct. The port needs to not be set to memcard or GCI etc.

This also needs XFB set to Real in order to display things in those earlier revisions.

The first time it gets to the second screen is 4.0-9154.

(Note: maybe unrelated but the revision 4.0-8340 caused unknown Pointer popups)

#6 Updated by ZephyrSurfer 10 days ago

In my testing the wiki is correct. The port needs to be empty not be set to memcard or GCI etc.

Below is testing with Default Settings other than XFB Real (Required to see something other than black screen and no Memcard set). No IPL.bin (Which greatly affects behaviour) or anything else.

3.0-797 (First to get past ARAM)
Gets to 2nd screen for first time.
Memcard set or not doesn't matter.

No longer gets past ARAM.

Some unknown pointer errors on ARAM test too

Gets to Second screen past the ARAM.
Needs No Memory Card/GCI set to do so though

Stops the unknown pointer popups on ARAM screen

The third screen now produces invalid read popups

Makes the third screen work for first time. No freeze at that point.

Makes the third screen produce unknown pointer errors

#7 Updated by ZephyrSurfer 10 days ago

That should have been 3.0-796. Oops

#8 Updated by ZephyrSurfer 10 days ago

That should have been 5.0-478 for point 4. Oops

Also available in: Atom PDF