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

Metal: Prevent usage of macOS-only APIs on non-macOS platforms #10886

Merged
merged 6 commits into from Jul 25, 2022

Conversation

OatmealDome
Copy link
Member

In the spirit of keeping the differences between my iOS fork and upstream minimal (and since the Metal backend already has support for iOS), here's a bunch of changes to make sure Metal APIs that are unavailable on non-macOS platforms are not used when targeting non-macOS.

@OatmealDome OatmealDome marked this pull request as ready for review July 23, 2022 17:58
@JosJuice
Copy link
Member

I don't know Apple, but this has been approved by the Apple knowers, so...

@JosJuice JosJuice merged commit 86bb290 into dolphin-emu:master Jul 25, 2022
@ShizCalev
Copy link

ShizCalev commented Jul 27, 2022

I'm getting Invalid Memory Access Locations errors when opening games since this commit.

Relevant issue report: https://bugs.dolphin-emu.org/issues/12995

@OatmealDome
Copy link
Member Author

Are you sure this bisect is correct? This PR changes code that only runs on macOS, and you are running Windows 10.

@ShizCalev
Copy link

ShizCalev commented Jul 27, 2022

Going through all the recent builds one by one, 5.0-16986 (this PR) is the first build where the issue starts to occur. 5.0-16979 and prior doesn't have the issue.

@OatmealDome
Copy link
Member Author

OatmealDome commented Jul 27, 2022

Do you have ESET NOD32? If not, what antivirus do you have?

@ShizCalev
Copy link

ShizCalev commented Jul 27, 2022

Hah, yes I have ESET nod32.

@OatmealDome
Copy link
Member Author

Please disable NOD32 or whitelist Dolphin. For whatever reason, NOD32 thinks that our fastmem code is something suspicious and blocks it. (If you are using other emulators with fastmem, this may also apply to them.)

@ShizCalev
Copy link

ShizCalev commented Jul 28, 2022

My issue was fixed in build 5.0-17025 via #10900. Thanks for the recommendation with ESET though!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
4 participants