fix(mcp): handle page crash event in Tab constructor

[o070256]

Summary

The Tab constructor registers listeners for various page events, including close, but not crash. These are two distinct Playwright events:

• close — fired when a page is closed normally
• crash — fired when the renderer process crashes (e.g. OOM, GPU crash, or certain unhandled conditions in complex SPAs)

When a renderer crash occurs, _onClose() is never called, leaving the tab as a zombie in the _tabs array — technically present but non-functional. Any subsequent tool call that tries to interact with the page will either hang indefinitely or fail with confusing errors like Target closed, without the MCP server properly recovering.

Change

Add a single crash event listener that calls the same _onClose() handler already used for close:

eventsHelper.addEventListener(p, 'crash', () => this._onClose()),

This ensures consistent cleanup regardless of how the page terminates.

Testing

Manually verified by navigating to a page that triggers a renderer crash — after the fix, the MCP backend correctly removes the tab and recovers on the next tool call.

[Skn0tt]

Hi, could you add a regression test for this? Look at page-event-crash.spec.ts for inspiration, a chromium-only test should suffice.

[o070256]

@microsoft-github-policy-service agree

[Skn0tt]

Now that I see the test, I'm not sure this is the right behaviour. When the page crashes, we want the agent to get some sort of a notification about it, not just the page to disappear. Similar to what we do in drainPendingUnhandledRejections. Could you open an issue and describe your scenario, so we can discuss how we fix it first?