Skip to content

Client crashes on shutdown with Watchdog timeout (Baritone CachedWorld$PackerThread hang)[Bug] #6674

Open

Description

@HexVortex-IO

Describe the bug

Meteor.Client.Error.zip

When quitting the game, the client hangs on shutdown and eventually crashes with java.lang.Error: Watchdog (Client shutdown from post-main).

According to the thread dump in the crash log, Baritone's background world caching threads (baritone.cache.CachedWorld$PackerThread) stay active saving region files and fail to terminate before the Minecraft client's shutdown watchdog timer expires.

Meteor Client Error.txt

Steps to reproduce

  1. Launch the game with Meteor Client / Baritone loaded.
  2. Join a world or server so Baritone initializes world caching threads in the background.
  3. Save and quit or close the client.
  4. Observe the client hanging on shutdown for ~30 seconds until the Watchdog forces a crash.

Meteor Version

26.2

Minecraft Version

26.2

Operating System

Windows

Before submitting a bug report

  • This bug wasn't already reported (I have searched bug reports on GitHub).

  • This is a valid bug (I am able to reproduce this on the latest dev build).

Activity

  1. Big-Iron-Cheems commented on Sep 21, 2026

    @Big-Iron-Cheems
    Collaborator

    This doesn't look like a Meteor related crash, it's an issue that was supposedly fixed in Baritone already here: cabaletta/baritone#5123.
    It has yet to be ported to the other versions so we can't do much about this.

  2. HexVortex-IO commented on Oct 9, 2026

    @HexVortex-IO
    Author

    Have you patched this error?

  3. masterpatrickpl-coder commented on Oct 10, 2026

    @masterpatrickpl-coder

    Interesting. Same thing has been happening to me. Going to take a look at this.

  4. HexVortex-IO commented on Oct 10, 2026

    @HexVortex-IO
    Author

    4. Interesting. Same thing has been happening to me. Going to take a look at this.

    Seriously. A reality is that only this 26.2 update have so many bugs and errors that any other versions ever released before 26.1.2 and below.

    Maybe if they will fix this error in this update or update it in next 26.3 update.

  5. masterpatrickpl-coder commented on Oct 10, 2026

    @masterpatrickpl-coder

    I second what @Big-Iron-Cheems is saying. This is a baritone error. It's not even a crash as such. It's just the minecraft client forcibly terminating a hung JVM.

  6. HexVortex-IO commented on Oct 10, 2026

    @HexVortex-IO
    Author

    2. This doesn't look like a Meteor related crash, it's an issue that was supposedly fixed in Baritone already here: cabaletta/baritone#5123.
    It has yet to be ported to the other versions so we can't do much about this.

    Have you patched this error in this version of meteor client?

  7. Big-Iron-Cheems commented on Oct 10, 2026

    @Big-Iron-Cheems
    Collaborator

    I think I made it clear the first time that this is a Baritone issue, not a Meteor one.
    There's nothing we can do on our end to address this.

  8. masterpatrickpl-coder commented on Oct 11, 2026

    @masterpatrickpl-coder

    What about the meteor baritone fork? that may have not been patched yet?
    I shall take a look

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions