Dolphin crashes with "Memory over 2GB" and "WriteRest op out of range" errors

[ryantargz]

Slippi Dolphin loads up fine, but after double clicking the melee iso, I'm met with multiple error dialogs: "Warning: Executable memory ended up above 2GB!" appears 1-3 times, then "Warning: WriteRest op out of range (0x9375d0f5 uses 0x7cd3a8)" appears 3+ times with different hex memory values. And then dolphin crashes/closes entirely.

One thing I found was that if I select a different CPU Emulator Engine other than "JIT Recompiler", the game would run, albeit very slow and not actually playable. But that leads me to believe the problem lies with the default recommended JIT Recompiler.

However, after toiling with it more, I HAVE found a workaround while using the default JIT Recompiler, which is to select the default ISO as melee and have it run the default ISO upon dolphin start, and to uncheck "Use Panic Handlers" (not sure if that part makes any real difference, other than squelching pop-up errors). With this method, I can get dolphin to start and run the game about 20% of the time, and the other 80% it will run and then crash/close immediately. Not sure why loading the ISO immediately on startup is more effective than dolphin loading my game folder list first and then choosing an ISO, but I hope that helps determine root cause.

I am running the following: Slippi 2.2.1 w/ an authentic SSBM 1.02 ISO macOS Catalina 10.15.6 Intel i9 9900k 32 GB Memory Radeon RX 5700 XT 8 GB

Also, for sanity, I ran the same SSBM ISO on a vanilla dolphin emulator (dolphin-emu.org) with 100% success. Build version was 5.0-11991.

[ryantargz]

After chatting in discord, it looks like this is a known issue with the older JIT Recompiler, and to be fixed with a mainline Slippi port. Until then, hopefully this temporary workaround helps some people get playing.

[DustinAlandzes]

It seems to happens, but I can always get it working by retrying a few times

here's system information/debugging information maybe it will help: https://gist.github.com/DustinAlandzes/38fe19219695af897d1175d7defde2c8

I can confirm that it works consistently with interpreter/cached interpreter but really slow

[NikhilNarayana]

Just wanted to make it clear that i added the won't fix label because we would rather move to mainline (where it has been fixed for a while) than fix an emulation issue.

[lararosekelley]

Curious if anyone has found a consistent workaround for this by messing with settings or something else - happens like 70% of the time for me when running in Slippi 2.2.3 on macOS 11.1. Just bumping so other Mac users have a reference point going into 2021.

[DustinAlandzes]

sadly no, I close everything and retry sometimes up to 50-100 times but it always works eventually

on Big Sur 1.11

---

I recorded an Automator script to press reopen on repeat for 10 minutes and it worked at least once.

retry slippi dolphin.zip

First un-check "Use Panic Handlers" (Config button > Interface Tab) :

Make sure "Start Default ISO on Launch" is checked (Config button > General Tab), and set melee 1.02 as your default iso (Config button > Paths Tab):

Start it when you get this popup and it will run for 10 minutes

hopefully you will eventually get this screen:

---

update: i'm using windows 10 in bootcamp now and it works so much better. maybe I could try linux too

[lilleswing]

Is there a ticket open on mainline for this? Has this been fixed on Dolphin? I was getting these issues on OSX today.

[JosJuice]

This was fixed a few years ago in mainline.

[zDEFz]

Still happening

[cnkeats]

Still happening

Slippi has not yet moved to mainline

[promilo]

I am also getting this error too on big surr, what does mainline mean?

[NikhilNarayana]

Mainline refers to official Dolphin.

[zDEFz]

Found a workaround:

1. Buy Parallels Pro for much cash
2. Add cheats for not rendering any background video on all levels. In particular, dream fountains is laggy.

[ryanmcgrath]

I'm looking for people who still experience this issue. Feel free to DM me in the Slippi Discord if this is you; I've been looking into this again lately and need a few people who can reliably reproduce this error to test some things.

(There's no guarantee it actually works, but this bug is maddeningly not reproducible on any of my machines - and I'd like to fix it if I can)

[VitamintK]

Your message could not be delivered. This is usually because you don't share a server with the recipient or the recipient is only accepting direct messages from friends.

[ryanmcgrath]

Ah, right. My username on Discord is knux#6598. DMs should be open (nobody's had issues in the past...). If nothing else you can email me: ryan@rymc.io

[zDEFz]

I'm looking for people who still experience this issue. Feel free to DM me in the Slippi Discord if this is you; I've been looking into this again lately and need a few people who can reliably reproduce this error to test some things.

(There's no guarantee it actually works, but this bug is maddeningly not reproducible on any of my machines - and I'd like to fix it if I can)

I left Discord because it requires you to have an mobile phone number assigned to it when you want to use it through a VPN. Additionally, deleting messages is not possible easily ... Discord isn't good.

On what version should I try to reproduce the issue?

[ryanmcgrath]

Latest version, and as noted in my last comment, my email is open if Discord is a blocker for you.

[zDEFz]

Latest version, and as noted in my last comment, my email is open if Discord is a blocker for you.

Weird, can't reproduce it anymore. It's perhaps 1 out of 10 where it spits this error message. Wondering what changed.

[ryanmcgrath]

Can probably close this now as I don't believe there's any further things that can be done here, short of what I did in PR #331.

[NikhilNarayana]

And now we wait for mainline