[BUG] Browser library processes are not closed properly when running from VS Code

[Lakitna]

Describe the bug

Whenever I run a test that includes Browser Library from VSCode (using the play button) some of the process tree remains. They are zombie processes, since the parent python.exe processes are closed.

Example where I tested with Chromium (screenshot from System Informer):

At first, I thought that this was a Browser Library issue, but it seems not the case. I tried all the following:

• When I use the CLI with a robot command, it works as expected ✅
• When I use the CLI with a pabot command, it works as expected ✅
• When I use the CLI with a robotcode command, it works as expected ✅
• When I use the VS Code play button provided by the robotcode extension, it creates zombie processes ❌
• When I use the PyCharm play button provided by the robotcode extension, it works as expected ✅

There seems to be something specifically related to the VS Code extension.

Steps To Reproduce
Steps to reproduce the behavior:

1. Open a project that uses Browser Library in VS Code
2. Find a test that opens a browser
3. Run a test from the IDE using the play button
4. Let the test finish (pass or fail, does not matter)
5. Observe in the task manager that a node.exe process and multiple browser processes remain

Expected behavior
All processes close after test is done. No zombie processes remain.

Screenshots/ Videos
Not applicable

Logs
Not applicable

Additional context
I'm not sure which info to provide. So please let me know what info can help you with this :)

AI / tooling disclosure
Not applicable

Desktop (please complete the following information):

• VS Code Version 1.128.0
• PyCharm Version 2026.1.4
• RobotCode Version 2.6.2
• OS: Windows 11
• Python Version 3.13.12
• RobotFramework Version 7.2
• Browser Library Version 19.10.0

[d-biehl]

need to investigate this. maybe the debugger is terminating to early.

[Lakitna]

For completeness stake, and unsurprisingly, this also happens in robotcode v2.7.0