2099-12-31 crash

[piplupness]

System model:

Old 2DS, but every model is affected by this

SysNAND version (+emu/redNAND version if applicable):

11.17.0-50E SysNAND

Entrypoint (How/what you're using to boot Luma3DS):

boot9strap

Luma3DS version:

v13.4

Luma3DS configuration/options:

Default EmuNAND: ( )

Screen brightness: (4)

Splash: (Off)

Splash duration: (3000 ms)

PIN lock: (Off)

New 3DS CPU: ( )

Hbmenu autoboot: ( )

--

Autoboot EmuNAND: ( )

Enable loading external FIRMs and modules: ( )

Enable game patching: ( )

Redirect app. syscore threads to core2: ( )

Show NAND or user string in System Settings: (X)

Show GBA boot screen in patched AGB_FIRM: ( )

--

Explanation of the issue:
Luma3DS 13.4 introduced the option to finally allow the end user to set any date from 2000-01-01 to 2099-12-31. Knowing the issues I already experienced by forcing 2099-12-31 using Godmode9 a year ago, I replicated it using the date and time settings on Luma3DS. Setting any date from 2000-01-01 to 2099-12-30 works just fine, console will not crash, but if changed to 2099-12-31, an arm11 exception occurs, with a mset crash. Mset crash can be avoided by setting the date to 2099-12-30 23:59 and waiting for the rollover, but the home menu can't handle that date and it will also crash. If the date is already set to 2099-12-31, changing the date to the same 2099-12-31 will not lead to a crash.
After the crash due to the date, the console will be unable to boot, returning arm11 exception with menu crash until the user decides to mess around in Godmode9 and changes the RTC date, or just waits maximum 24 hours for the system to rollover to 2000-01-01.

From the experiment I have done using Godmode9 a year ago, just the advance to 2099-12-31 will not crash, but once the console tries to load or open another process, it will crash. For example letting the date advance on 2099-12-31 in Pokémon Omega Ruby didn't result in a crash, game worked fine until the home button was pressed, that's what led to the exception.

Steps to reproduce:

1. Open System Settings

2. Select Other Settings

3. Select Date & Time

4. Select Today's Date

5. Set the date to 2099-12-31

6. Press OK on the Activity Log warning

Dump file (if applicable):
00000002.dmp = mset crash after confirming the date
00000003.dmp = menu crash after booting on 2099-12-31

crash_dump_00000002.dmp
crash_dump_00000003.dmp

[TuxSH]

Thanks for reporting!

It's possible that HOME Menu tries to calculate the time of the next day and/or set an alarm, what happens if the time offset is sufficiently negative (that is, GM9 displays a lower date&time), instead of being zero? As

the user decides to mess around in Godmode9 and changes the RTC date

suggest that it is zero.

Also the patch I made it's pretty dumb, it replaces some references to "50" to "99". For now I've just updated the release notes.

[piplupness]

In this example console date was set to 2099-12-31 and Godmode9 to the day I made the issue (2026-04-03), so the offset wasn't zero.

But decided to give it a try by setting 2099-12-31 on Godmode9 using offset = 0, console will still crash on boot.

That quote in your comment means the user can fix the problem by changing the day one day early or late to get 2099-12-30 or 2000-01-01, good dates that allow the 3DS to boot and eventually fix the date properly

[ipkpjersi]

Would it make sense to temporarily cap the maximum console date to December 30 instead of December 31? That way, it may prevent accidental crashes from happening until this can be fixed.