What happened?

Several users reported their framerates dropping incredibly low (1-2 fps) for seemingly no reason, then coming back to normal once again for either seemingly no reason or because they reloaded shaders. This has been reported with multiple shaderpacks.

Screenshots

No response

Relevant log output

No response

Iris and Minecraft Version

Iris/Sodium 1.1.0 for Minecraft 1.1.7

Are you running Sodium along with Iris?

Yes

Operating System

Windows and Linux

What is your GPU?

several

Java Version

Java 16

Additional context

This has been reported both with and without other mods

Should be fixed in latest commits

Would be helpful to have Spark profiles of this - maybe it can be tracked down to a certain function misbehaving. Or maybe this is another case of the entity rendering memory leak?

Is this #419 as well?

I do not believe this is identical to #419 since #419 is unfixable in-game. Once it happens, it is permanent unless you leave the world.

Screenshots from users who experience the bug

It seems that panning the camera causes extreme issues while using Lithium and Starlight fixes it.

Also happens without shaders.

I wonder if this happens with the Sodium 1.17 branch: https://github.com/CaffeineMC/sodium-fabric/

If it happens without Iris that would help narrow it down.

Confirmed Sodium issue inherited from upstream, keep open for monitoring until it is fixed

placing or breaking block really fast causes this for me, along with it happeining a few seconds after joining the world, but it goes waay after 10 seconds

and theres a cpu usage spike sometimes, and gpu is totaly unused

I did not notice this issue in 1.16.5, across 4 PCs ranging from Windows 8 to 10, GTX 560 to 2080Ti, i3-2320 to i9-9900ks.

In 1.17 there were heavy frame drops that could be related to not having sodium, or could be related to just this? It was hard to tell, and I removed it from all PCs.

I was very excited by the new Iris+Sodium release which did run better overall but unfortunately the drop to zero still happens. I ended up removing it rather than disabling it. I am still trying to work out what exactly causes it but there seem to be particular areas where it's more likely to kick in (or maybe I'm just in those areas more often) - I'll take any advice on what I can do to test and help.

The Ram usage is also EXTREMLY High, as soon as it hits that point of starting to Lag.
So, maybe theres something wrong with the RAM usage/handling?

The Ram usage is also EXTREMLY High, as soon as it hits that point of starting to Lag.
So, maybe theres something wrong with the RAM usage/handling?

This is a known memory leak in sodium

The Ram usage is also EXTREMLY High, as soon as it hits that point of starting to Lag.
So, maybe theres something wrong with the RAM usage/handling?

This is a known memory leak in sodium

oh ok.

I am also experiencing the same issue with Iris Shaders + Sodium. I am getting similar memory leak issues with the newer implementation of Sodium with the fix provide in build 506 which was implemented in 1.17 fork as well. This crash is very regular and predictable basis. For me this point happens at the 45 minute mark with Iris Shader + Sodium and BSL Shaders. Would guys like the crash reports?