-
Notifications
You must be signed in to change notification settings - Fork 812
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
Incompatible with LWJGL 3.2.3 (used by ARM64 builds) #748
Comments
This is because the "M1 Hack" bundles LWJGL 3.2.3. The latest version available in MultiMC (and used by Minecraft) is 3.2.2, and there was a breaking change in 3.2.3:
|
so you could technically just make a failsafe where it changes to memFree if it detects LWJGL 3.2.3 |
I was able to run this as well as other Minecraft instances using a fork of the M1 hack. It ships 3.2.2 AFAICT. |
I tried that fork and faced the same crash; JDK 16 Minecraft 1.17.1, latest Sodium. |
This commit works around the issue: IrisShaders@7491e3a |
Same here on an M1. Getting super high frame rates 70-120FPS with 300+ mods but stutters down to 7-20 when moving. Disconnecting from server gives me the sodium crash. Now that I know it is the M1 hack I’ll try in regular compatibility Rosetta mode. |
We'll merge the workaround from Iris into Sodium 0.3.1. |
This is now fixed in Sodium 0.3.1. |
was messing around with settings in sodium 0.3.1 iris doesnt work for me but i dont really use it |
Version information
mc1.17.1-0.3.0+build.494
Reproduction Steps
org.lwjgl.system.MemoryUtil.memFree
method)Crash Report file
crash-2021-07-08_19.15.01-client.txt
Additional information
This is likely due to Sodium's usage of certain
org.lwjgl
methods with the "M1 MultiMC Hack" located here https://github.com/yusefnapora/m1-multimc-hack. I have tried various forks of it with no success, either. I do not expect this to have a high priority as it would be done to support a hack-y setup. Older versions of Sodium seem to not encounter this crash issue.The text was updated successfully, but these errors were encountered: