tailcat: close all backend resources - #19
Open
0xcadams wants to merge 3 commits into
Open
Conversation
0xcadams
marked this pull request as ready for review
August 29, 2026 00:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Makes Tailcat shutdown fully release the in-process networking backend, including active netstack connections.
Why
locoBackend.Close currently closes only the WireGuard engine and network monitor. The gVisor netstack, dialer, and event bus remain alive, so an accepted TCP connection can stay blocked after Server.Close and repeated ephemeral Tailcat instances retain resources.
Changes