fix: restart browser automatically on disconnect in server mode#1610
Merged
Conversation
kitsuyui
force-pushed
the
fix/audit-browser-dead-state-no-restart-001
branch
2 times, most recently
from
June 5, 2026 17:26
2d8ac86 to
18ffffe
Compare
gh-counterPR gate
Repo dashboard
Reported by gh-counter |
When the Playwright browser crashes or disconnects (OOM, runtime error), listen for the 'disconnected' event and restart it automatically. The server handler reads from a mutable browser reference via a getter closure, so in-flight requests pick up the new browser after restart. Also rename createServer/createHandler to accept a browser getter (() => Browser) instead of a direct Browser instance, enabling the mutable reference to be shared across reconnects.
kitsuyui
force-pushed
the
fix/audit-browser-dead-state-no-restart-001
branch
from
July 9, 2026 01:42
18ffffe to
3c28eb2
Compare
Code Metrics Report
Details | | main (88661b5) | #1610 (e5896b4) | +/- |
|---------------------|----------------|-----------------|-------|
- | Coverage | 87.1% | 84.1% | -3.0% |
| Files | 11 | 11 | 0 |
| Lines | 226 | 234 | +8 |
| Covered | 197 | 197 | 0 |
- | Code to Test Ratio | 1:0.5 | 1:0.5 | -0.1 |
| Code | 1760 | 1775 | +15 |
| Test | 1003 | 1003 | 0 |
+ | Test Execution Time | 12s | 10s | -2s |Code coverage of files in pull request scope (76.9% → 66.6%)
Reported by octocov |
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.
Summary
main()shared one PlaywrightBrowserinstance across all requests with no recovery path when it disconnected (OOM, runtime crash, Playwright error). Once dead, every request returned 502 until a manual server restart.'disconnected'event listener on the browser that automatically restarts it and re-registers the listener. The server handler reads the current browser through a() => Browsergetter closure, so the new instance takes effect without restarting the HTTP server.createHandlerandcreateServernow accept agetBrowserFn: () => Browserparameter instead of a directBrowserinstance, enabling the mutable reference to propagate on reconnect.Changed files
src/server/index.ts— browser auto-restart logic inmain(), updatedcreateHandler/createServersignaturessrc/server/index.spec.ts— updated test callsites to passgetBrowserFn: () => browserTest plan
npx tsc --noEmit— type-checks passnpx biome check .— no lint errorsnpx vitest run src/lib/headers.spec.ts src/index.spec.ts— unit tests passsrc/server/index.spec.ts— server still responds correctly via the newgetBrowserFnAPITrade-offs
getBrowser()throws during a restart attempt, the error is swallowed and subsequent requests will fail until the next disconnect fires. This keeps the server alive but may silently delay recovery. A future improvement could add a retry loop or health-check endpoint that reflects browser state.createServer({ browser })→createServer({ getBrowserFn })is a breaking change for direct callers ofcreateServer; all in-repo usages have been updated.