-
Notifications
You must be signed in to change notification settings - Fork 258
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
[BUG] Building Library\Bee\artifacts\Android\a7sem\2b6k1szry106.o failed [RAM ISSUE?] #2008
Comments
These are the 2 wanted files. Thank you |
Are you suggesting that because that fixed the problem? If you've got bad RAM there's nothing we can do to fix that. |
Hi! If you have any other suggestions or there are some other files that I need to attach, please let me know. I am looking for a fix but I ran out of solutions.. |
It's probably just a run of the mill compiler bug. Workarounds are typically disabling optimization for whatever function has the crash, or rewriting the code differently. Seeing as you're using Unity and the problem comes from the editor source, you probably don't want to be doing that. You could probably disable IL2CPP for local development, but idk if that's something you'd want to do for a shipping configuration. |
Hello! Mono is working for me, thank you! Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. |
For the guys that are coming here from Unity, here is a post with another issue opened on the Unity forum: https://forum.unity.com/threads/fresh-unity-instal-opening-with-compile-errors.1570849/ . I hope this is not spam or anything. |
Which NDK version are you actually using? You didn't say, and there's really nothing we can do without that info. |
Unity 2022.3 has ndk version r23b(23.1.7779620) |
Oh, that hasn't been supported for years. Try updating. If it's still broken, reopen with updating artifacts (they're not portable across versions). |
Description
My configuration:
Is it something related to RAM?
Is there a way to fix it other than removing 2 RAM pieces?
Affected versions
Canary
Canary version
No response
Host OS
Windows
Host OS version
Windows 11
Affected ABIs
x86_64
Build system
ndk-build
Other build system
No response
minSdkVersion
5.1
Device API level
No response
The text was updated successfully, but these errors were encountered: