Maico Spiering

this still doesn't seem fixed for the 1.13 release mainly the MC-98209 part,

as this seems to be incomplete but i was easily able to reproduce ill add the way to reproduce here.

create a new world in 18w21a

find a body of water

underwater dig a hole straight down for about 4 blocks should be fine

from above it looks like the hole is full of water particles and water color and all.

but if you go into the hole it will look as if you are outside of the water but you will still see particles.

and you float like you would in water but you don't need to breath

and there wont be an error showing in the logs

I would like to add how i can consistently cause this error.

i've set my render distance to 2 chunks and generate a new world in 18w21a.
then just move in 1 direction.

if you enable f3 you will see memory usage go up and never drop.

And after a minute or so the game will crash

but i would like to note that my memory was not nearly full yet like 1gb of the 3gb allocated

Can confirm 18w21a.

will spam this error in the log when loading chunks

I used to have this bug, but got it fixed today.
ill share my findings.

first things i had but the bug was still there
latest videocard drivers
jvm arguments: -Xmx4G
java version: 1.8.0_05

the bug was fixxed after the following changes:
java version: 1.8.0_20
jvm arguments: -d64 -Xmx4G

so far i have been able to switch rendering distance ingame without the need for restart or vbo being on or off.
i used to have this problem above 20ish chunks