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

Iris crashes on 1.21.3, Mixin conversion failed #2556

Open
HarryH2O opened this issue Dec 5, 2024 · 5 comments
Open

Iris crashes on 1.21.3, Mixin conversion failed #2556

HarryH2O opened this issue Dec 5, 2024 · 5 comments

Comments

@HarryH2O
Copy link

HarryH2O commented Dec 5, 2024

What happened?
A bug happened! My “iris” shader crashes, but the game starts fine after uninstalling!
I want my game to launch normally!

Steps to reproduce the bug:

Use the HMCL-3.6.11 launcher
Install 1.21.3 + Fabric 16.0.8 + fabric API - 0.106.1
Start the game in the same environment as me and observe the phenomenon
Related information:
My compurer: 2020 Macbook Pro M1 8+256
OS: macOS 14.7.1 (23H222) on MacBookPro17,1 (arm64)
Processor: 8 cores, Apple M1
Memory: 8G physical memory, 4G swap space
Java: JDK 23.0.1
Minecraft version: 1.21.3 (official)
Iris module version: 1.8.1+mc1.21.3 fabric
Loader: Fabric 16.0.8 + Fabric API - 0.106.1 + 1.21.3
Minecraft Launcher: HMCL-3.6.11

Other Mods:

Screenshots
No response

Log output
1.21.3.json
crash-2024-12-04_23.13.04-client.txt
hmcl.log
hs_err_pid56347.log
latest.log
minecraft.log

Minecraft Version
Minecraft 1.21.3

Iris Version
iris 1.8.1

Operating System
macOS 14.7.1 (23H222) on MacBookPro17,1 (arm64)

What is your GPU?
Apple M1

Additional context
The game throws 'ExceptionInInitializerError' on initialization
The error involves a failed Mixin conversion of the 'net.caffeinemc.mods.sodium.client.render.immediate.CloudRenderer' class.
It may have something to do with Shader loading or Mixin configuration.

In fact, I used a genuine Microsoft account to launch the game and downloaded the mod from the Iris official website I hope you can take users' issues seriously and not conclude without verification that they are using pirated products
Image
Image

@Poopooracoocoo
Copy link

You're using Iris 1.8.1 and Sodium 0.6.0-beta.3.

You need to update Sodium. https://modrinth.com/mod/sodium/version/mc1.21.3-0.6.2-fabric

@HarryH2O
Copy link
Author

HarryH2O commented Dec 5, 2024

Thank you very much for your method, but after I updated "Sodium" and its related mods, the HMCL launcher sent me an unknown error related to a graphic error. I suspect this may still be related to Iris.Please you review my error report.

Logs:
1.21.3.json
crash-2024-12-04_23.13.04-client.txt
crash-2024-12-05_12.01.12-client.txt
hmcl.log
hs_err_pid56347.log
hs_err_pid69531.log
latest.log
minecraft.log

Here are the relevant questions I have summarized using AI and inferred based on my own experience, which may be helpful to you!

The Java application encountered a fatal error, causing the Java Runtime Environment to crash. Here are the key points from the error analysis:

Error Type: SIGSEGV (0xb), which is a segmentation fault. This typically indicates that the program attempted to access a part of memory that was not allocated or is not accessible.

Error Location: The error occurred in the glpLLVMGetFunctionGlobalVariableUse function within the libGLProgrammability.dylib library. This suggests that the issue may be related to OpenGL or a related graphics library.

Java Thread: The error occurred in the "Render thread," which is typically associated with graphics rendering.

Stack Trace: The stack trace shows multiple calls to libGLProgrammability.dylib, further supporting the assumption of a graphics library issue.

System Information: The application is running on macOS 14.7.1 with an Apple M1 chip. The system has 8 GB of memory and 8 cores.

Java Version: The Java version is 23.0.1+11, which is a relatively new version.

Possible Causes:

Graphics Library Issue: Since the error occurred in libGLProgrammability.dylib, it could be a bug in OpenGL or a related graphics library.
Memory Access Issue: Segmentation faults are usually related to memory access problems, such as invalid memory references or uninitialized pointers.
System Compatibility Issue: Given that it is running on an Apple M1 chip, there may be compatibility issues related to this architecture.

@Poopooracoocoo
Copy link

https://shaderlabs.org/wiki/Shaderpacks and the Vanilla Plus website, CF page, and MR page say that the Vanilla Plus shaderpack does not support Apple Silicon (ARM64, M1)

@HarryH2O
Copy link
Author

HarryH2O commented Dec 5, 2024

So is there a solution? If not, I apologize for disturbing you

@Poopooracoocoo
Copy link

The linked website shows you which shaderpacks support Apple Silicon GPUs

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

2 participants