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

Texture changing/reloading causes client-side freezing for 7-15 seconds

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Works As Intended
    • None
    • Minecraft 1.5, Minecraft 1.5.1, Minecraft 1.5.2, Snapshot 13w19a, Snapshot 13w21a, Snapshot 13w25a, Snapshot 13w25b, Snapshot 13w25c, Minecraft 1.6, Minecraft 1.6.1, Minecraft 1.6.2, Minecraft 13w37a, Minecraft 13w37b, Minecraft 1.7
    • Windows 7 64-bit Professional
      4.00GB (3.75GB Usable) RAM
      3.00 GHz AMD Athlon(tm) II X2 250 Processor
      124GB Unused Hard Drive Space
      64-bit Java 1.7.0_11
    • Unconfirmed

      Changing or reloading Minecraft's texture pack, in any situation, causes an absurd delay where the client is entirely unresponsive. This applies to:

      • Changing texturepacks via the main menu, under Options
      • Changing texturepacks ingame via the menu
      • Server textures activating when you join a server
      • Server textures deactivating when you leave a server
      • Refreshing textures when pressing F3+T

      The delay ranges anywhere between 7 and 15 seconds for me. The lower end of that range (viz. around 7 seconds) appears when activating a texturepack, even if it only modifies a single texture. The delay tends to be almost twice as long (viz. up to 15 seconds) when switching back to the default texture pack.

      This is disruptive, if not altogether deadly, when joining a server with custom textures: the client is unresponsive for at least 7 seconds, during which time any number of bad things can happen (especially if you logged off in the middle of danger).

      I should note that, in the past, texturepack changes have not caused client freezing in excess of 3 seconds for me (often as little as about 1.5 seconds), which is understandable.

            Unassigned Unassigned
            wolfiemario WolfieMario
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: