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

Unit Tests fails with System.AccessViolationException #1256

Open
ataparia opened this issue Oct 21, 2024 · 0 comments
Open

Unit Tests fails with System.AccessViolationException #1256

ataparia opened this issue Oct 21, 2024 · 0 comments

Comments

@ataparia
Copy link

Hi Team,
The library works great on all platforms i.e. Windows(64), iOS and Android.

However, when I try to run the unit tests on Windows(64), the call to SetBusyTimeoutAsync fails with the following error message:
"System.AccessViolationException: 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt"

Even weird is the fact that the same unit tests runs fine for other developers on my team and it was working fine on my old laptop even though the old and the new laptop are both running Windows 11 on x64 processor.

Has anyone encountered this issue as well?

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

No branches or pull requests

1 participant