Minecraft Version

Minecraft 1.21

Iris Version

iris-fabric-1.8.0-beta.3+mc1.21.1.jar

Sodium Version

sodium-fabric-0.6.0-beta.1+mc1.21.jar

Operating System

Windows 11

What is your GPU?

Intel(R) Iris(R) Xe Graphics

Java Version

Java 21

Reproduction Steps

1. join a server or a local world freshly created
2. play for just half a minute
3. the screen suddenly froze but the Game WON'T Crash(i wait for a few minutes and manually stop the game)
4. game control using mouse and keyboard is still available, only the screen won't change
   latest.log

Crash Report file and latest.log

No crash logs are available! See latest.log as the attachment.

Additional context

This crash is similar to issue #2445.
However i'm using Iris 1.8 Beta 3(the latest stable version also leads to this problem).
I'm glad to provied anything required for this issue

I'm commenting here because the similar issue was closed. Here's what I've experienced:

I was impacted by the mesa problem on Linux (I'm using steam deck). Once mesa updated, I was able to load the SEUS PTGI shaders that I prefer without the artifact problem.

While I was waiting for the mesa update, I experimented with several other shaders, particularly Bliss. I experienced the game apparently locking up, definitely with Bliss, but I believe with every shader I tried. I don't know about the claim of the game still running, but not being displayed. That might be the case for me, I don't know how to test it.

Having only used SEUS previously, I assumed the other shaders weren't as stable. But now that I can use SEUS again, it's also freezing. I'm using Iris 1.8 beta 4. I updated that recently (I didn't note what the previous version was) and it made no difference regarding this problem.

Here's what I've observed that might be of use. Freezing seems to be triggered by loading a lot of chunks. If I begin from a fresh restart and play in the overworld without traveling much, it seems like I could play indefinitely with no problem. If I begin from a fresh restart and travel a lot with elytra immediately, there seems to be no problem. I haven't tried a super-long flight. But if I play for a while, I don't know how long, maybe 30 minutes, and then I try to travel, it can cause a freeze. If I play in the End for a while and return to the overworld and attempt to travel, it tends to freeze. If I play for a while in the overworld and enter the nether, it tends to freeze. If I begin from a fresh start in the overworld and use the nether to travel to another overworld location, it tends to freeze.

To avoid this problem, I have to restart before a session with shaders, and I have to disable shaders while traveling.

This is arriving on my game too when I join a singleplayer world for eg. I can add that I can see my memory filled up to 100% causing freeze and eventually crash after. So it's maybe a memory leak problem.

Shader used : complentary reimagined
Minecraft version : 1.21.0
Windows 11
Java 21
Sodium version : mc1.21-0.6.0-beta.2-fabric (even all iris 1.21 and sodium for mc 1.21 versions)
GPU : Nvidia Quadro T2000 with Max-Q Design

As a solution for me, I try to update the DRIVER of Intel(R) Iris(R) Xe Graphics to latest, instead of the OEM version. This greatly help to reduce the problem. The freezing problem seldom happened after that.
PS: After this problem I move my game to my new PC with NVIDIA RTX 4060TI 16G and this 100% solve the problem. So, spending some money do make sense : )

As a solution for me, I try to update the DRIVER of Intel(R) Iris(R) Xe Graphics to latest, instead of the OEM version. This greatly help to reduce the problem. The freezing problem seldom happened after that. PS: After this problem I move my game to my new PC with NVIDIA RTX 4060TI 16G and this 100% solve the problem. So, spending some money do make sense : )

I'm using a Steam Deck, so this isn't an option for everyone. Could someone look into how these changes impact the problem?

This problem may have been fixed by recent Prism and/or MESA updates. I just had a session where I did what I wanted, didn't have to save, didn't have to exit and re-run MC, didn't have to restart, and it didn't lock up. I haven't been watching Prism issues. It may be notable that two Prism updates back, when I ran it, a dialog popped up to set the minimum/maximum RAM allotment. Maybe the problem was Prism wasn't actually using the user RAM setting and wasn't allotting enough? Non-expert observations here...