ben

I also have this issue and it affects all versions that Op mentioned.  Happens when I use either a Amd Ryzen 3700x and Amd Ryzen 5800x cpu.  Tested different motherboard/ram configs.  Reinstalled Windows/minecraft to no avail.

Specs : Ryzen 5800x

            Nvidia 2080ti

            16gb ram

            Nvme hard drive

            Windows 10

i just added it, if you cant see it lmk

Vanilla minecraft 1.15.2, clean install

This is happening with my 2080ti, even in single player, new world, clean install of windows 10, no background apps running other than obs (but obs doesnt cause it).

I tested a gt710 in the same system, and it isnt stuttering anywhere near as much, and sometimes doesnt stutter at all when crossing chunk borders.

When testing with both cards, I used stock nvidia control panel settings, all default.  No overclocking. 

Nvidia driver 432.00 (stock windows 10 driver), although the driver version doesnt make any difference at all.

I tested with vsync on/off, framerate cap at 60fps/120fps/off.  A mixture of all, makes no difference.

Temperatures are in check, no overheating.  I tried underclocking the 2080ti memory/core clock in afterburner, and it didnt make any difference.

 Whenever i put the 2080ti in the computer, crossing chunk borders = stutters.  The 2080ti passes all stress tests, such as unique heaven and furmark, left for hours, no crashing/artifacts.

Maybe worth a mention.. When the mem : empties (garbage collection by pressing f3), there is a small micro stutter each time.  Alot worst on the 2080ti, hardly present on the gt710.

Strangely, i set up another computer, ryzen 3700x, 16gb ram, diifferent chipset, new clean install of windows 10, tried both the gt710 and 2080ti, new minecraft world, and still the 2080ti stutters when crossing chunk borders.   Its not the psu as i tested two different power supplies.

In game resolution / refresh rate seems to make no difference to the stuttering at chunk borders.  I tested both 1080p and 1440p.

Please watch the video below :

https://streamable.com/fwzx2u

or

https://youtu.be/it9nrux193w

I updated to the latest java version today, jre-8u241-windows-x64, and set it in the Minecraft Launcher, the game still stutters when memory fills up.

Hi again, just an update.

Frametimes being reported in afterburner :

In single player frametimes are bouncing between 9ms-24ms

In multiplayer frametimes bouncing between 9ms - 30ms

Framerate cap set at @ 120fps in Minecraft, framerate seems to be stable (but stuttering continues

I disabled afterburners power monitoring before testing, as I know that can cause micro stuttering.  Didnt help.  I have also tried disabling windows game mode, to no avail.

Edit 2 : I was mistaken, Frametimes are hitting as high as 60ms, so 9ms - 60ms fluctations. 

Thanks for your input.

I would like to add, it is happening in the single player world too.  I checked frametimes using msi afterburner and they are spiking really high each time minecraft stutters.

 I have tried setting a framerate cap inside Minecraft, and the same stutter occurrs.  I can limit the framerate to 120 or 60, which it can sustain easily, but Minecraft will still stutter each time the memory fills up.

I have this same issue on Minecraft PS4.

I'm not sure if it has already been mentioned, but turning off Dynamic FOV in the options, video settings, clears up the issue for me instantly.  But it is a compromise as I'm quite fond of Dynamic FOV.

I removed optifine, and the same happens in vanillia Minecraft 1.11.2.  Pressing w three times quickly triggers the sprint zoom in/out bug.  Tested in Hypixel and Mc Central.

Hello,

I found a way to reproduce it easily and it happens everytime. 

To reproduce the sprint bug, on a game server (happens in Hypixel in the Lobby)

Press W W W (holding the last W), pressing the keys very quickly.  For some reason pressing W three times consequetively causes the screen to get stuck zooming in and out.

My config: Minecraft 1.11.2, OptiFine_1.11.2_HD_U_C7, No other mods. Keyboard - Razer chroma.

I tried reinstalling and it still crashes, still don't know how to check for 16w06a

I have no clue what that means, I am very new you'll have to go step by step 😞

I always thought that this bug was because redstone wire is unpredictable in the order that it updates blocks. This can be exemplified by having a line of droppers all being powered by the same line of redstone dust. How far an item goes down the line of droppers depends what order the redstone decides to update the droppers in. If it is intended for redstone to be slightly indeterminate, then this is not a bug, however I would argue that it is.

Would this also be related to not being able to properly summon SmallFireballs through spawners or command blocks, as well as them disappearing after re-logging?

Discovered something about this, if you summon a FallingSand with time not equal to 0 on a block of the proper type, the client will delete the block, but the server will not. Also the client will be able to see the FallingSand created this way.

Spawners are supposed to spawn entities in range you gave, SpawnRange only affects the x and z range. This works as intended, Not sure about the pig though.

I had a similar problem in the latest snapshot, but it was with command blocks that didn't have anything to do with teams.
I was telling the command blocks to make minecart with command blocks, then I crashed when I entered the command that makes them.
The error said that it "Recieved string length longerr than maximum allowed (88 > 64)".
This was also on a server.

it is very annoying