Skip to content

Got error.ConnectionResetByPeer on receive. This indicates that a previous message did not find a valid destination. #3511

Open

Description

@calebstenberg

It happens when leaving a world on windows.
This was fixed(#1322) but seems to have come back again.
The fix for #1322 added a delay in network.zig line 1943, looking at the git blame it was changed in PR #2009 to use a different delay method.

Git bisect found #3376, but that just finds an error that already existed.

Activity

  1. added
    bugsomething isn't working in the intended way
    on Aug 12, 2026
  2. calebstenberg commented on Aug 12, 2026

    @calebstenberg
    ContributorAuthor

    That might not actually be it, because #2009 was Nov 2025. I do know that it was working fine in 3.0 so somewhere between then and now

  3. IntegratedQuantum commented on Aug 13, 2026

    @IntegratedQuantum
    Member

    Does it happen reliably? If so, could you use git bisect to find the commit that actually caused this?

  4. calebstenberg commented on Aug 13, 2026

    @calebstenberg
    ContributorAuthor

    git bisect is sick!
    It returned #3376 which may not be helpful if the error was added but had actually been happening before
    And yes it happens every time I leave a world, at least in singleplayer

  5. IntegratedQuantum commented on Aug 16, 2026

    @IntegratedQuantum
    Member

    Could also check some older versions (e.g. version 0.0.0)? I wonder if it maybe happened all along (or maybe was caused after a windows update), but was just missed because the error was handled improperly for some time.

  6. calebstenberg commented on Aug 16, 2026

    @calebstenberg
    ContributorAuthor

    Could also check some older versions (e.g. version 0.0.0)? I wonder if it maybe happened all along (or maybe was caused after a windows update), but was just missed because the error was handled improperly for some time.

    I can, but I am mostly unfamiliar with git, would you happen to know the right git commands to keep one commit but revert back to an earlier version?

  7. IntegratedQuantum commented on Aug 16, 2026

    @IntegratedQuantum
    Member

    git checkout 0.0.0

  8. calebstenberg commented on Aug 20, 2026

    @calebstenberg
    ContributorAuthor

    But I need to also keep the fix commit so the error shows up, or I need to keep a local commit where I fix it at least. How do I keep an arbitrary commit when using git bisect?

  9. Argmaster commented on Aug 20, 2026

    @Argmaster
    Collaborator

    I am not sure what you mean, but if you are very unfamiliar you might be thinking about a branch? Git history in general is a large linked list of commits. Branch points to an arbitrary commit giving it a name. Pardon me if I misunderstood your needs.

  10. IntegratedQuantum commented on Aug 20, 2026

    @IntegratedQuantum
    Member

    But I need to also keep the fix commit so the error shows up

    The fix commit should only be necessary after #2009 which messed up the windows error constants, and that was merged after version 0.0.0

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 in the intended way

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions