Harry Howes
More than one avatar was detected! There might be multiple accounts sharing this same name.
Comments
I'd like to add to this by saying this has only been an issue with oak trees for me. Every other tree I'm able to break without experiencing a harsh lag spike. Every now and then I'll be able to cut down an oak tree without any spikes, but that's around one every 50 trees if that. Can also report that it has been very consistent with me, reloading the save does nothing and I've had the save for around a week now, have also created new saves and every time I experience the same issue.
After some testing I discovered that setting biome blending to no higher than 5x5 resulted in no more lag spikes (if not highly reduced spikes). I spoke to some of the guys on the OptiFine discord and after a bit of back and forth we settled on an explanation one of them gave..
"in older versions, leaves had 2 properties, each of which could be in 2 states. they could be player-placed or natural, and they could be checking for decay, or not checking. a block update would always set the "check for decay" state to true, and that was it. the next time the leaf got a random tick, if the leaf is checking for decay AND there are no logs nearby AND the leaf is natural (not player placed), then the leaf would decay, and cause block updates to its neighbors. the neighbors would then start checking for decay, and the process repeats, very slowly.
in 1.13 though, mojang added a new property to leaves: their distance to the nearest log. every time a leaf gets a block update, it waits for 1 game tick, and then checks for nearby logs and updates its distance accordingly. the important thing here though is that it gives out block updates during this process, so its neighbors will ALSO check for nearby logs only one tick later, and the process repeats very quickly.
what I suspect is happening is that mojang dumbly decided to re-render the sub-chunk every time a leaf changes its distance property. so suddenly breaking a single log will cause a huge number of nearby leaves to change their distance, which then creates equally many chunk re-renders, and finally, an even huger number of biome checks."
To summarize, mojang seems to have written horrendously poorly optimized code. Which OptiFine fixes.