Skip to content

fix(mcp): close browser process on backend disposal#40040

Closed
RedhatEnt wants to merge 1 commit intomicrosoft:mainfrom
RedhatEnt:fix-1458
Closed

fix(mcp): close browser process on backend disposal#40040
RedhatEnt wants to merge 1 commit intomicrosoft:mainfrom
RedhatEnt:fix-1458

Conversation

@RedhatEnt
Copy link
Copy Markdown

Summary

  • API (createConnection) and extension backend factories had no-op disposed callbacks, leaving browser processes running after browser_close or client disconnect
  • Added browserContext.close() + browser.close() to both factories, matching the existing CLI factory behavior

Fixes microsoft/playwright-mcp#1458

The API (`createConnection`) and extension server backend factories had
no-op `disposed` callbacks, leaving browser processes running as zombies
after `browser_close` or client disconnect. Mirror the existing CLI
factory behavior: close the browser context and browser on disposal.

Fixes: microsoft/playwright-mcp#1458
@RedhatEnt
Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree company="Noetic Emergence Consulting LLC"

Copy link
Copy Markdown
Member

@pavelfeldman pavelfeldman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] playwright-cli close leaves headed Chrome process running (zombie in app switcher)

2 participants