-
Bug
-
Resolution: Fixed
-
1.18.0.20 Beta, 1.17.40.23 Beta, 1.17.40.21 Beta, 1.17.30.22 Beta, 1.17.30.21 Beta, 1.17.30.20 Beta, 1.17.11 Hotfix, 1.17.10, 1.16.220, 1.14.30 Hotfix, 1.14.60 Hotfix, 1.16.221 Hotfix, 1.17.30, 1.17.32, 1.17.33, 1.17.34
-
Confirmed
-
Multiple
-
349991
To repro, Fill 5 shulkers full of items, place those five shulkers into a hopper. Face that hopper into an empty shulker. Next steps prove that it isn't client side
Large amounts of lag will occur. The easiest way is to go to another dimension or an area a long way away (as a way to show it is server/host side not client side), and place gravity blocks while the hopper with 5 full shulkers are loaded on a second players device. This will cause entity rubber banding and block placement lag server wide.
Empty or partially full shulkers seem to cause less lag, this leads to the assumption that the data in the shulker is a contributing factor to the lag. Based upon this, the assumption is that the data in the shulker is put a transfer request then canceled ever tick,
https://youtu.be/eTPg_hXs8hM world file is attached.
A gametest was created to directly show the measurable lag. see BedrockTechnicalTestTools.mcaddon
lag:shulker_lag is the test for bring the shulkers in
lag:check_lag uses the time function in java script to measure the time between ticks...
- is duplicated by
-
MCPE-136154 Optimize the hopper full check function Hopper::_isFullContainer
- Resolved
-
MCPE-137940 Hoppers cause immense lag when attempting to place blocks/items into the chest with no open slots
- Resolved
- relates to
-
MCPE-27167 Shulker boxes filled with items cause incredible lag
- Reopened