It's the same bug, it was closed before being properly fixed. I see no purpose in creating a new ticket.
This is still broken in 1.14.3 pre2. I took a map out of an item frame and it does not refresh, and is stuck with the green arrow.
It got fixed by game restart.
It does not occur 100%, i.e. I can't reproduce it now. Maybe the item frame needs to be there when you load the save, or needs to exist for some time.
I thought we might finally have some use for this item, and it doesn't work 😞
Really don't understand why these were added in the first place, but this seems like an oversight. It's the only item I ever wanted to compost. Well, and rotten flesh, but that doesn't work either.
I'll add that it seems to be partly related to the "don't render invisible chunks" optimization, as sometimes a whole sections of the world flash out of existence and back in as I look to sides. The chunks that get stuck invisible always loaded for me when I walked into the chunk, albeit sometimes with a small delay. This is similar to a bug before 1.14 where some chunks would stubbornly refuse to render until you broke a block in them.
This is still broken in 1.14 Pre-Release 5, are you sure it's really fixed? it seems pretty broken to me
Okay I tested again and it is related to render distance, and "several minutes" was clearly an exaggeration on my side. I had distance set to 32 from trying to debug MC-138114 (it didn't help).
But there is a regression in save times - my results with world seed 77 (setup: Linux, SSD, i5-6400 2.7GHz, 16GB RAM)
Render distance 32:
1.13.2 - saving a new world took 2 seconds
try 1: 1.14pre1 - saving took 20 seconds for a brand new world
try 2: 1.14pre1 - a new world i explored a little by flying around in creative, saving took 40 seconds and then crashed with MC-147754
Render distance 20:
1.13.2- saved almost instantly
1.14pre1 - saved in 2 seconds
1.14pre1 - the more explored world, saved in 8 seconds (maybe it didn't crash because it didn't try to generate the buggy chunk?)
Had this with a new world generated in the pre-release 1, so its not necessarily related to migrating old save data or optimizing.
it shouldn't be sea pickles, because they don't spawn in cold ocean, but i have a similar experience with breaking blocks.
I discovered the glitch goes away when you go to Optimize World and check Clear Cache Data before running the optimize. This might help debugging
this can be closed as they completely rewrote the loading screen
the same thing always happened to torch smoke, there'll be an old issue for it somewhere
edit: it's MC-3455 (closed with WAI - which I disagree with)
A very similar issue affects turtles when burying their eggs on a beach. I'm sure there is (and should be) a separate issue for that, but it might have the same underlying cause.
just had it happen in the 19w02a snapshot, the loading screen got stuck at 100% and didn't proceed until I moved the mouse
not sure what you think will come from spamming the bug tracker with duplicates like this, during Christmas holidays when nobody is in the Mojang office
similar but different mechanic - placing lava so it flows over water and creates smoothstone, the lava doesn't flows into seagrass, as if it was a full block
MC-130333 which describes this behavior is marked as duplicate, but i think that's incorrect
[media]Still affects the last snapshot of the year. Booo
also cant craft it, and I tried many different shapes of the recipe
similar chunk error in seed 50a right next to the outpost, this doesn't look like a natural ravine to me
[media][media]here it is
Same issue in Vivaldi (chrome based). I found that to fix it, you have to go to browser settings, search "language", and in the list of languages, delete all but en-us and en (also keep your native language, of course). Weird bug, this is the only site where I had this problem.