microlinkhq / browserless / 38419042268

77%

push

github

fix: respawn Chrome when it stops answering CDP (#988)

* fix: respawn Chrome when it stops answering CDP

A hung browser stays connected, so the disconnect path never replaces it and every later context waits out the 180s protocol timeout.

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix: kill a hung Chrome instead of closing it over CDP

browser.close() sends another DevTools command, so a browser that already stopped answering would hold the respawn lock for the protocol timeout.

Co-authored-by: Cursor <cursoragent@cursor.com>

* refactor: make the hung Chrome respawn easier to follow

The close decision and the single retry were nested harder than the behavior they describe.

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix: close a context that arrives after the create timeout

When createBrowserContext lost the race against the timeout, a context
that Chrome created afterwards was never closed. On the first attempt the
browser is killed, but on the second attempt the browser stays alive and
the context stayed open on it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

2104 of 2388 branches covered (88.11%)

Branch coverage included in aggregate %.

52 of 53 new or added lines in 2 files covered. (98.11%)

7693 of 10285 relevant lines covered (74.8%)

58437.87 hits per line