You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a233fcd
Browse filesBrowse the repository at this point in the historyBrowse files
devstack front door: a client that goes closes the runtime's connection whole
A client's end done, the front door only half-closed the runtime's. workerd
keeps a WebSocket connection whose client closed (half-closed, or with a
Close frame), so each such pass waited on the runtime for good: a thread
and two sockets per closed socket, the shell's own watch among them. A
repro of reloads, each closing two WebSockets, held 28,207 threads and
56,413 fds in ten minutes, and then connections were reset (module loads
failed ERR_CONNECTION_RESET). Now, the client gone, the runtime's
connection is closed whole, as a proxy does once its client goes.
Test: a client that goes, from a runtime that keeps a 101'd connection
open and silent after it: the pass ends (before: it never did).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments