Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Force SyncGPU on pause #5274

Closed
wants to merge 1 commit into from
Closed

Conversation

sepalani
Copy link
Contributor

@sepalani sepalani commented Apr 15, 2017

This PR is an attempt to fix random crashes that happen when the emulator hits a breakpoint (and probably happen when the emulator is paused). It seems that these crashes only happen on dual-core with SyncGPU off, switching to single-core or enabling SyncGPU seems to fix them.

I try to address these by enabling SyncGPU before pausing the emulator. However, even if it works I'm not sure that's the best way to sync the GPU since I mess with the config on the fly. So I'm open to any suggestions.

Regardless, this fix the following issue for me: https://bugs.dolphin-emu.org/issues/10132
And might fix this one as well: https://bugs.dolphin-emu.org/issues/10071

Ready to be reviewed & tested.

@degasus
Copy link
Member

degasus commented Apr 16, 2017

AFAIK PauseAndLock should also pause the GPU thread. Is this broken in the latest builds?

@sepalani
Copy link
Contributor Author

It does happen on latest builds, not sure if it means that's broken, though. Are you sure PauseAndLock can't desync the GPU on dual core? If it can't, then there might something wrong in CPU::EnableStepping or CPU::Break which don't (or can't?) call it, I suppose.

@ghost
Copy link

ghost commented Nov 27, 2021

I occasionally experience this issue of crash and freeze using the latest version of dolphin on playstore. Can this PR maybe solve my issue?

@ghost
Copy link

ghost commented Nov 27, 2021

How can I test this? there's no apk build 🤔

@gordonfreeman01
Copy link
Contributor

@Gamemulatorer As this PR is quite old, you'd need to resolve the merge conflicts with the latest code version then run your own build to create and APK for testing. You may want to go to the source branch and build the old version but the sheer amount of improvements made since then would render the need for updating the PR a must.

@sepalani
Copy link
Contributor Author

Closing this since it can be circumvented by using single core and I don't think there is a simple/reasonable way to address the issue.

@sepalani sepalani closed this Aug 10, 2022
@sepalani sepalani deleted the fix-bp-crash branch August 10, 2022 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants