Hey guys, I'm having this problem. While playing Minecraft, it just freezes for a second.
I'm playing with 32 chunks and 16 simulations. To solve this, I recommend leaving these settings unchanged
Please help.
One short instance is hard to go off, but my usual guess in such a situation would be garbage collections, but your stutter does not coincide with the memory allocation dropping (and memory allocation also drops numerous times with no stutter).
How often does this occur? Is it reproducible while crossing that same spot?
I see you're using Fabric, Sodium, and immediately Fast, but there's others I'd recommend if you're not using them. Namely, Lithium, Ferrite Core, and Entity Culling.
A render distance of 32 and simulation distance of 16 can be taxing, although I'd expect that hardware to handle it.
A couple suggestions I'd have would be the following...
1. A few users with nVidia hardware are noticing memory leaks. I don't know if this isolated to driver version 581.80 but I think so far all users had that driver version, and you are using something slightly older, but I'd watch your VRAM use in task manager and see if yours is frequently growing (and dropping) and/or if the "copy" graph has frequent activity along with it.
2. If you're not using it, I'd switch to the ZGC in generational mode.
3. 3 GB memory allocation for a render distance of 32 seems a bit low to me. I'd personally go with something closer to 6 GB or 8 GB at that distance (my recommendation may err higher because I like to have overhead in case I raise the render distance higher, and I use the ZGC along with the C2ME mod, both of which need more memory, so you can probably get by with less otherwise).
If you still have issues, I would then suggest trying a modded instance without content modifications (and only using optimization mods) and seeing if it still occurs.
Hi, thanks for your help.
No. It happens in different places. In completely random places.
Regarding the driver, I forgot to update
What's ZGC? Aren't those JVM arguments? I tried to figure it out, but....
it so hard xD
Regarding mods, I don't think I use overly demanding mods.
Thanks for your help. I'll reply later with information on video memory usage.
UPD:By the way, I have these JVM arguments in Prism Launcher
Regardless of whether you update drivers, watch the VRAM use patterns while playing and see if there's any correlation (and if your VRAM is showing rapid growth at times, such as when stationary in chunks).
If those are your JVM arguments then you're already using the ZGC, in which case I would definitely recommend raising memory allocation. I don't even see the allocation amount in your JVM arguments so I don't know if the launcher you're using has a separate field for that or something.
It might be worth only trying the essential (to use the ZGC) JVM arguments, which are "-XX:+UseZGC -XX:+ZGenerational" and adding the others back if the problem remains without them. Even the second one might not be essential with Java 23+ but you can go ahead and leave it even if it's redundant.
None of those mods look like they would be causing it to me, but if you exhaust all other options, troubleshooting anything is always going down to the bare essentials and adding things back in steps to try and isolate the source of the issue. I would add Lithium and Ferrite Core though.
Rollback Post to RevisionRollBack
"'Tis foolishness! If all were so easy, why, none would suffer in this world!"
Okay. I haven't noticed anything in the task manager yet.
BUT!! When I played with the Legacy lag locker, I didn't experience any lag at all. Could this mean something?
My translator translated it a little wrong.
I meant that when I played Minecraft through the Legacy Launcher, this didn't happen. I also recorded a more detailed video of my problem.
So it doesn't occur with the legacy vanilla launcher, but it does with the third party launcher you tried? The legacy vanilla launcher is what I use so i don't have experience or knowledge with third party ones.
Are the JVM arguments you're using the same in both launchers? If they are, then... no idea. But at least you have a fix?
I haven't played Java much since 1.21.4 and I know there's some performance differences in later versions since they are making changes to rendering, so I tried 1.21.10 and here what I get with a newly created world.
Compared to 1.21.4, my observations are as follows.
I might be imagining it (and my sample size is only one world), but fresh chunk generation seems quite a bit faster than 1.21.4? It should be noted I'm using C2ME in both, which speeds this up, and that mod is working towards using GPU acceleration but I'm not sure if it's doing that or not in the public 1.21.10 release yet.
As a result, frame rate when moving (at least when chunks are generating/loading) is lower, but otherwise it feels equally smooth as 1.21.4 does.
Displaying the frame time graph and internal server time graph vastly reduces frame rate. I'm familiar with the F3 screen possibly reducing frame rate, but in 1.21.4 the difference occurs with the display of the F3 screen itself (adding the graphs has no further reduction). That's quite the observer effect.
But there's no major outlier stutters like you're experiencing.
My hardware isn't too far off from yous; I have a bit better of a CPU and you have a bit better of a GPU. Minecraft is typically more CPU reliant, but I wouldn't expect you to have severe stutters on that CPU.
So I'm once again wondering if there may be a VRAM leak in nVidia's drivers. Your stutter only shows in the client, not the internal server. Watch the VRAM display on the GPU tab in task manager while playing, and when you get one of these stutters, switch to see what VRAM use looks like.
If that's not it, then I don't know. But it sounds like you have a solution with the legacy client?
Rollback Post to RevisionRollBack
"'Tis foolishness! If all were so easy, why, none would suffer in this world!"
As it turned out, Legacy Launcher - steals data. I decided to change it.
But when playing the legacy launcher I didn’t use any jvm arguments. I will look at the VRAM leak again today
Yo
I did everything like you said (hope it's correct)
And it seems like there are no leaks. At least I don’t see any. In the video, I’m playing with c2me
Okay, that does rule out the VRAM leak issue that some others have reported.
At this point, I'm not sure what could be causing that then. However, I notice there are spikes in CPU use during both stutters, which lines up because stutters are usually caused by lack of CPU time. So that would be the clue I'd work off of. My guess is that something (either with the game itself, or outside it) is causing system resources to be tied up momentarily. But I'm not sure what it might be.
(Unrelated, but I'd recommend right-clicking the CPU graph in task manager and changing it to show logical processors, because overall utilization is bad at reflecting things like this on multi-core CPUs, and I'd suspect one core or thread is ~100% when this happens.)
Does this happen only in window mode? Have you tried full screen?
Have you made sure the nVidia control panel settings are at their default settings? Is nVidia shadow play running and auto recording clips or videos? The encode graph is reflecting some activity.
Could even be an attached USB device? High polling rate mouse?
Have you tried other versions? Such as 1.21.4 or 1.20.1? Is this isolated to 1.21.10, or do older versions have similar issues?
I'm grasping at straws here because I can see clues suggesting something is tying up CPU time which is likely the cause of the stutters, but I'm not sure what it might be.
Earlier you said switching from a third party launcher to the vanilla legacy launcher stopped the issue? Or did I misunderstand that? You later said the legacy launcher steals data (?) so I'm a bit confused on that part.
Yes. This didn't happen with the legacy launcher.
But then videos and articles came out about the unreliability of that launcher, and I decided to change it.
UPD: What launcher are you using? I was wondering if changing the launcher would solve the problem?
I use the legacy vanilla launcher. I've had no major reliability issues with it. I'm not sure what data it could be stealing since it is not a third party thing, so by definition, it can't do that.
The vanilla launcher has its drawbacks (it recently forgot saved profiles for some people, myself included, when the Halloween update was reverted), and third party launchers have their benefits (such as simplifying installation of mods or management of profiles and directories), but the inverse can also be true. I recall instances where third party launchers or clients were a risk for user data, or were causing detrimental performance behaviors of their own. This thread seems to be one such example. Whether the behavior of something matters to you is going to depend on your own circumstances. Keep in mind that the legacy and Microsoft store vanilla launchers are also different things. Sometimes, the issues you hear of effect only one (usually the latter) and not the other.
Anyway, if the issue isn't present when using the vanilla legacy launcher, then you've narrowed it down. When you said one launcher had the issue but another didn't, that's why I asked if the same JVM arguments were being used in both cases. The issue may be with the JVM arguments (if they are different) as opposed to the launcher. If the JVM arguments are the same, then it's something else the launcher is doing/causing.
Rollback Post to RevisionRollBack
"'Tis foolishness! If all were so easy, why, none would suffer in this world!"
Hey guys, I'm having this problem. While playing Minecraft, it just freezes for a second.
I'm playing with 32 chunks and 16 simulations. To solve this, I recommend leaving these settings unchanged
Please help.
One short instance is hard to go off, but my usual guess in such a situation would be garbage collections, but your stutter does not coincide with the memory allocation dropping (and memory allocation also drops numerous times with no stutter).
How often does this occur? Is it reproducible while crossing that same spot?
I see you're using Fabric, Sodium, and immediately Fast, but there's others I'd recommend if you're not using them. Namely, Lithium, Ferrite Core, and Entity Culling.
A render distance of 32 and simulation distance of 16 can be taxing, although I'd expect that hardware to handle it.
A couple suggestions I'd have would be the following...
1. A few users with nVidia hardware are noticing memory leaks. I don't know if this isolated to driver version 581.80 but I think so far all users had that driver version, and you are using something slightly older, but I'd watch your VRAM use in task manager and see if yours is frequently growing (and dropping) and/or if the "copy" graph has frequent activity along with it.
2. If you're not using it, I'd switch to the ZGC in generational mode.
3. 3 GB memory allocation for a render distance of 32 seems a bit low to me. I'd personally go with something closer to 6 GB or 8 GB at that distance (my recommendation may err higher because I like to have overhead in case I raise the render distance higher, and I use the ZGC along with the C2ME mod, both of which need more memory, so you can probably get by with less otherwise).
If you still have issues, I would then suggest trying a modded instance without content modifications (and only using optimization mods) and seeing if it still occurs.
"'Tis foolishness! If all were so easy, why, none would suffer in this world!"
If you're having performance concerns with Minecraft, I hope this may prove useful.
A retrospective of the most important game to me (or, a try to stay awake while I never stop talking about something challenge).
Hi, thanks for your help.
No. It happens in different places. In completely random places.
Regarding the driver, I forgot to update
What's ZGC? Aren't those JVM arguments? I tried to figure it out, but....
it so hard xD
Regarding mods, I don't think I use overly demanding mods.
Thanks for your help. I'll reply later with information on video memory usage.
UPD:By the way, I have these JVM arguments in Prism Launcher
-XX:+UseZGC -XX:+ZGenerational -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -XX:+PerfDisableSharedMem -XX:+UseDynamicNumberOfGCThreads
Regardless of whether you update drivers, watch the VRAM use patterns while playing and see if there's any correlation (and if your VRAM is showing rapid growth at times, such as when stationary in chunks).
If those are your JVM arguments then you're already using the ZGC, in which case I would definitely recommend raising memory allocation. I don't even see the allocation amount in your JVM arguments so I don't know if the launcher you're using has a separate field for that or something.
It might be worth only trying the essential (to use the ZGC) JVM arguments, which are "-XX:+UseZGC -XX:+ZGenerational" and adding the others back if the problem remains without them. Even the second one might not be essential with Java 23+ but you can go ahead and leave it even if it's redundant.
None of those mods look like they would be causing it to me, but if you exhaust all other options, troubleshooting anything is always going down to the bare essentials and adding things back in steps to try and isolate the source of the issue. I would add Lithium and Ferrite Core though.
"'Tis foolishness! If all were so easy, why, none would suffer in this world!"
If you're having performance concerns with Minecraft, I hope this may prove useful.
A retrospective of the most important game to me (or, a try to stay awake while I never stop talking about something challenge).
Okay. I haven't noticed anything in the task manager yet.
BUT!! When I played with the Legacy lag locker, I didn't experience any lag at all. Could this mean something?
I have no idea what "legacy lag locker" is.
"'Tis foolishness! If all were so easy, why, none would suffer in this world!"
If you're having performance concerns with Minecraft, I hope this may prove useful.
A retrospective of the most important game to me (or, a try to stay awake while I never stop talking about something challenge).
My translator translated it a little wrong.
I meant that when I played Minecraft through the Legacy Launcher, this didn't happen. I also recorded a more detailed video of my problem.
So it doesn't occur with the legacy vanilla launcher, but it does with the third party launcher you tried? The legacy vanilla launcher is what I use so i don't have experience or knowledge with third party ones.
Are the JVM arguments you're using the same in both launchers? If they are, then... no idea. But at least you have a fix?
I haven't played Java much since 1.21.4 and I know there's some performance differences in later versions since they are making changes to rendering, so I tried 1.21.10 and here what I get with a newly created world.
Compared to 1.21.4, my observations are as follows.
I might be imagining it (and my sample size is only one world), but fresh chunk generation seems quite a bit faster than 1.21.4? It should be noted I'm using C2ME in both, which speeds this up, and that mod is working towards using GPU acceleration but I'm not sure if it's doing that or not in the public 1.21.10 release yet.
As a result, frame rate when moving (at least when chunks are generating/loading) is lower, but otherwise it feels equally smooth as 1.21.4 does.
Displaying the frame time graph and internal server time graph vastly reduces frame rate. I'm familiar with the F3 screen possibly reducing frame rate, but in 1.21.4 the difference occurs with the display of the F3 screen itself (adding the graphs has no further reduction). That's quite the observer effect.
But there's no major outlier stutters like you're experiencing.
My hardware isn't too far off from yous; I have a bit better of a CPU and you have a bit better of a GPU. Minecraft is typically more CPU reliant, but I wouldn't expect you to have severe stutters on that CPU.
So I'm once again wondering if there may be a VRAM leak in nVidia's drivers. Your stutter only shows in the client, not the internal server. Watch the VRAM display on the GPU tab in task manager while playing, and when you get one of these stutters, switch to see what VRAM use looks like.
If that's not it, then I don't know. But it sounds like you have a solution with the legacy client?
"'Tis foolishness! If all were so easy, why, none would suffer in this world!"
If you're having performance concerns with Minecraft, I hope this may prove useful.
A retrospective of the most important game to me (or, a try to stay awake while I never stop talking about something challenge).
As it turned out, Legacy Launcher - steals data. I decided to change it.
But when playing the legacy launcher I didn’t use any jvm arguments. I will look at the VRAM leak again today
Yo
I did everything like you said (hope it's correct)
And it seems like there are no leaks. At least I don’t see any. In the video, I’m playing with c2me
Okay, that does rule out the VRAM leak issue that some others have reported.
At this point, I'm not sure what could be causing that then. However, I notice there are spikes in CPU use during both stutters, which lines up because stutters are usually caused by lack of CPU time. So that would be the clue I'd work off of. My guess is that something (either with the game itself, or outside it) is causing system resources to be tied up momentarily. But I'm not sure what it might be.
(Unrelated, but I'd recommend right-clicking the CPU graph in task manager and changing it to show logical processors, because overall utilization is bad at reflecting things like this on multi-core CPUs, and I'd suspect one core or thread is ~100% when this happens.)
Does this happen only in window mode? Have you tried full screen?
Have you made sure the nVidia control panel settings are at their default settings? Is nVidia shadow play running and auto recording clips or videos? The encode graph is reflecting some activity.
Could even be an attached USB device? High polling rate mouse?
Have you tried other versions? Such as 1.21.4 or 1.20.1? Is this isolated to 1.21.10, or do older versions have similar issues?
I'm grasping at straws here because I can see clues suggesting something is tying up CPU time which is likely the cause of the stutters, but I'm not sure what it might be.
Earlier you said switching from a third party launcher to the vanilla legacy launcher stopped the issue? Or did I misunderstand that? You later said the legacy launcher steals data (?) so I'm a bit confused on that part.
"'Tis foolishness! If all were so easy, why, none would suffer in this world!"
If you're having performance concerns with Minecraft, I hope this may prove useful.
A retrospective of the most important game to me (or, a try to stay awake while I never stop talking about something challenge).
Yes. This didn't happen with the legacy launcher.
But then videos and articles came out about the unreliability of that launcher, and I decided to change it.
UPD: What launcher are you using? I was wondering if changing the launcher would solve the problem?
I use the legacy vanilla launcher. I've had no major reliability issues with it. I'm not sure what data it could be stealing since it is not a third party thing, so by definition, it can't do that.
The vanilla launcher has its drawbacks (it recently forgot saved profiles for some people, myself included, when the Halloween update was reverted), and third party launchers have their benefits (such as simplifying installation of mods or management of profiles and directories), but the inverse can also be true. I recall instances where third party launchers or clients were a risk for user data, or were causing detrimental performance behaviors of their own. This thread seems to be one such example. Whether the behavior of something matters to you is going to depend on your own circumstances. Keep in mind that the legacy and Microsoft store vanilla launchers are also different things. Sometimes, the issues you hear of effect only one (usually the latter) and not the other.
Anyway, if the issue isn't present when using the vanilla legacy launcher, then you've narrowed it down. When you said one launcher had the issue but another didn't, that's why I asked if the same JVM arguments were being used in both cases. The issue may be with the JVM arguments (if they are different) as opposed to the launcher. If the JVM arguments are the same, then it's something else the launcher is doing/causing.
"'Tis foolishness! If all were so easy, why, none would suffer in this world!"
If you're having performance concerns with Minecraft, I hope this may prove useful.
A retrospective of the most important game to me (or, a try to stay awake while I never stop talking about something challenge).