Recent update triggering this error on auto-update

DaRkL3AD3R · 03-16-2023, 01:23 PM #1

The portable emulator folder for this hasn't moved from this directory since it was put there back in like 2009. Only after an update about a week ago or so did this error start appearing. It happens after updating Dolphin after it finishes the update and goes to launch again. Clicking OK makes it launch without fault after until the next update.

***MayImilae*** · 03-16-2023, 03:43 PM #2

Which update specifically?

DaRkL3AD3R · 03-16-2023, 03:50 PM #3

I wish I knew. No way to find out since I have to let it update to trigger the bug and doing so will push me to latest dev build.

***MayImilae*** · (This post was last modified: 03-16-2023, 06:41 PM by MayImilae.)

If we don't know what build started it then to be very hard to track down. :/

So try this - Do a fresh download of the latest dev build from our download's page, and set up a new separate portable installation in a different spot. Copy over your user folder (and just your user folder), and use that for a while and see what happens. Let's see if that fixes it.

DaRkL3AD3R · 03-17-2023, 09:56 AM #5

I downloaded the 2nd most recent dev build and extracted it to a fresh folder, copied my User folder alone over to it. Then opened it up and set it to check for dev branch updates. Closed Dolphin and let it do the auto update, and it had the same exact error popup.

I'm pretty sure the problem is having spaces in the directory path. I have it setup as "D:\[My Name]'s Documents\Emulators\GameCube" and if you look at the error, the path starts after the space. So perhaps something changed in the past week or so that involves how the path to the executable is found and that's the source of the problem.

***MayImilae*** · (This post was last modified: 03-17-2023, 11:22 AM by MayImilae.)

This is a bit sooner than "about a week ago" but 5.0-18935 is the most likely cause of this.

I'm not sure how we can test to confirm that though...

DaRkL3AD3R · (This post was last modified: 03-17-2023, 12:49 PM by DaRkL3AD3R.)

Three and a half days ago could be about right. It feels a lot more like a week to me lately though lol but yeah most likely culprit. It's hard to test because I'd have to pull a version at least 2 versions back from that one and then have the updater only pull to the very next version, before this particular build to see if it errors out. Then have it pull the next build linked above and see if that creates the error. But I see no way to selectively choose which builds to update only the latest or nothing, so I don't think there's much more I can do from there.

Just an idea: could we revert that merged pull request and see if the updater still causes issues when another update happens after?

***MayImilae*** · (This post was last modified: 03-17-2023, 01:48 PM by MayImilae.)

AdmiralCurtiss has already looked at the version in question and deduced a possible fix - https://github.com/dolphin-emu/dolphin/pull/11666

But because this is updater related, that PR will have to be merged and then another on top of that before we can really know if that fixes it.

DaRkL3AD3R · 03-17-2023, 02:50 PM #9

I'll be happy to keep an eye on things and update this thread if/when the problem is resolved. Thanks for the help!

DaRkL3AD3R · 03-19-2023, 04:25 PM **#10**

Just updated and it's fixed! Instantly opens Dolphin after the updater is complete. Thanks all for the quick fix and allowing me to keep this super old directory path intact Smile