fix(kopiaui): fix status-poll socket leak in KopiaUI - #5574
Open
ElCruncharino wants to merge 1 commit into
Open
Conversation
pollOnce() never drained the response body on a non-200 status, and never handled the "timeout" event on the request (the timeout option added in kopia#3055 only emits an event, it doesn't abort anything on its own). Both leave the underlying socket open forever instead of being freed, one leaked connection per affected 3-second poll for as long as the app runs.
ElCruncharino
force-pushed
the
fix/kopia-ui-status-poll-socket-leak
branch
from
August 24, 2026 23:13
674868a to
27ad296
Compare
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.
Found this while debugging a growing number of ephemeral ports held open
by kopia on my machine, traced back to the KopiaUI status-poll loop.
pollOnce()inapp/public/server.jsnever drains the response body on anon-200 status, and never handles the
timeoutevent on the request (thetimeoutoption added in #3055 only emits an event, it doesn't abortanything on its own). Both leave the underlying socket open instead of
being freed, one leaked connection per affected 3-second poll for as long
as the app runs.
This adds handling for both cases so the socket is released every time.