Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-10101

Lag Spiking on Block Updates Leads to Multi-Place/Multi-Destroy



    • Type: Bug
    • Status: Resolved
    • Resolution: Duplicate
    • Affects Version/s: Minecraft 1.4.7
    • Fix Version/s: None
    • Environment:
      Operating System: Windows 7 Home Premium, Service Pack 1
      Processor: Pentium(R) Dual-Core CPU E5300 @ 2.60 GHz 2.60 GHz
      Graphics: Intel (R) G33/G31 Express Chipset Family GMA 3100
      Installed RAM: 4.00GB
      Java: Version 7 Update 15 (64-bit)
    • Confirmation Status:
    • Game Mode:


      Upon placing a block or destroying one, there will be a huge lag spike about 5-50% of the time (depending on how fast the game is running otherwise: 60-70fps = 5%, 10-15fps = 50%) that will result in 2-3 blocks being placed or destroyed with even the briefest of clicks instead of the intended one. This makes the game virtually unplayable because the placement and destruction of blocks becomes essentially out of the player's control. I have done personal testing to confirm that it is not a hardware glitch; both my and others' experiences have been that the problem occurs only in Minecraft (not in any other application) and persists whilst using the trackpad instead as well as after replacing the mouse with a new one. This bug will still occur with no other applications open and no other users logged in. It sometimes takes a little while to materialize, and sometimes will not materialize at all; however, it is reproducible and persistent, striking perhaps every other to every third time I play and often setting in within fifteen minutes of beginning play. Getting the game to lag to about 10-20fps can help the issue become far more readily apparent, although I have seen it occur at frame-rates as high as 73fps.


          Issue Links



              • Assignee:
                bronsonboy Drew Bronson
              • Votes:
                1 Vote for this issue
                2 Start watching this issue


                • Created: