Page becomes unresponsive after Disconnect → Re-attach in attach mode (CDP state not fully released)

Two issues when using attach mode to connect to an already-running Edge browser with
--remote-debugging-port=9222:

Bug 1: Page becomes unresponsive after re-attach (Disconnect → Re-attach)

1. First attach to a browser tab works correctly — page is fully interactive.
2. Click Disconnect (not Terminate — browser stays open, tab remains).
3. Attach again to the same tab (same URL, same browser, same port).
4. The page becomes completely unresponsive — no clicks, no scrolling, no interaction
   at all. The page appears frozen/locked.
5. Only restarting VS Code restores the ability to attach normally, but the cycle
   repeats: 1st attach OK → disconnect → 2nd attach broken → must restart VS Code again.

This suggests that js-debug does not fully release CDP domain state (e.g. Debugger,
Overlay, Input) on disconnect, leaving the page in a "still-being-debugged" state that
blocks user interaction on the next attach.

Bug 2: Page becomes sluggish after several hot reloads while attached

While attached, after a few HMR (Hot Module Replacement) updates, the page becomes
noticeably laggy. This worsens progressively and suggests a memory leak — possibly CDP
sessions or event listeners accumulating across hot reloads without being cleaned up.

To Reproduce

Bug 1:

1. Launch Edge with --remote-debugging-port=9222
2. Open a web app (e.g. https://example.com) in a tab
3. In VS Code, start debugging with the attach config below
4. Verify the page is interactive (click links, scroll, etc.) — works fine
5. Click the Disconnect button in the debug toolbar (not Terminate)
6. Start debugging again with the same config (attaching to the same tab)
7. Try to interact with the page — page is completely frozen/unresponsive
8. Only restarting VS Code allows a successful attach again

Bug 2:

1. Attach to a running web app (same config)
2. Make code changes to trigger HMR hot reloads 3-5 times
3. Observe increasing page lag/stuttering with each reload

Log File

(Will attach trace log if requested)

VS Code Version: 1.115.0

Environment:

• OS: macOS (Darwin)
• Browser: Microsoft Edge (Chromium)
• Debug port: 9222 (--remote-debugging-port=9222)
• Debug type: msedge / attach

Launch config:

{
    "type": "msedge",
    "request": "attach",
    "name": "my-app",
    "urlFilter": "https://example.com/*",
    "webRoot": "${workspaceFolder}",
    "port": 9222,
    "timeout": 1000,
    "sourceMaps": true,
    "skipFiles": ["node_modules/**", "<node_internals>/**"]
}

Additional context

• This is not related to any extensions — reproduced with all other extensions
  disabled.
• Bug 1 is 100% reproducible: first attach always works, second attach (after
  disconnect) always fails.
• The issue is specific to Disconnect (page stays open). Using Terminate (which closes
  the page) does not exhibit this problem since the tab is destroyed.
• Suspect that on disconnect, js-debug leaves CDP domains like Debugger, Overlay, or
  Runtime in an enabled state on the target, which then blocks page interaction when a
  new debug session attaches.