Placing a pushable block in the path of a falling block with slime blocks being pushed by 0 tick pistons at low tick rates induced by lag (<6 TPS) can create a ghost block

Steps to reproduce the bug:

1. Create or join a singleplayer world

2. Build a lag machine until you consistently get higher than 160 ms on the “Integrated Server @ (Current tick rate) / 50 ms” label on the F3 menu.

3. In a 2 by 2 hole, place 2 redstone torches on opposite sides from each other.

4. On one side of the 2x2 hole, place 2 slime blocks on the block above only one of the torches, and then place one slime block on top of the two slime blocks on one side, and then a falling block on the other.

5. On the upper layer, build 2 sticky pistons on the slime block side such that the pistons are on the edge of the hole.

6. Build an upwards facing regular piston directly above each sticky piston.

7. Connect the redstone from the sides of the hole next to each torch to the pistons such that each redstone line feeds straight into the upper piston.

8. Place a block on one side of the machine

Expected Result:

The block does not alter the properties of any other block and remains on the placed side.

Actual Result:

The block sometimes moves to the alternate side of the machine, leaving a ghost block on the placed side.