RooCode leaves all Node/Python MCP servers open after VSCode is fully closed

[privacyguy123]

I am on Windows 10 with VSCode 1.100.0

App Version

3.16.5

API Provider

Requesty

Model Used

N/A

🔁 Steps to Reproduce

1. Open VSCode and use RooCode with MCP servers enabled
2. Close VSCode
3. Check a Process Explorer app:

💥 Outcome Summary (Optional)

I expect this is called a "memory leak" maybe? It seems like a moderate enough issue that I've seen across versions ~3.13 until now.

📄 Relevant Logs or Errors

Unsure how to retrieve these if it's after VSCode has already closed.

EDIT: As a small side issue that's also related (but might needs it's own ticket) MCP servers that are explicity DISABLED seem to be also getting loaded in. (Sorry I just noticed #2797)

[dosubot]

Hi @privacyguy123! I'm Dosu, your friendly bot here to help you out while you wait for a human maintainer. I can assist with bugs, answer questions, and guide you on becoming a contributor. Let's tackle this together!

The issue you're experiencing with Node.js and Python MCP servers remaining open after closing VSCode might not be directly addressed in the current RooCode documentation or codebase. However, there are some recent updates related to MCP server management that might be relevant.

In version 3.16, improvements were made to capture MCP server errors and display them in a new "Errors" tab, along with enhanced error logging ^[1]. Additionally, version 2.2.5 introduced the ability to enable or disable individual MCP servers in the settings, which might help manage server processes more effectively ^[2].

For configuration, RooCode uses mcp_settings.json for global settings and .roo/mcp.json for project settings, which might include options for managing server lifecycle ^[3][4]. You might want to check these configuration files to see if there are any settings related to server shutdown behavior.

If the issue persists, it could be beneficial to check for any open issues or discussions in the RooCode repository that might address this specific problem.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[hannesrudolph]

@privacyguy123 are there any other vs code instances open at the time of these rogue processes?

[privacyguy123]

@privacyguy123 are there any other vs code instances open at the time of these rogue processes?

No, or else I wouldn't have said "after VSCode is completely closed." I can repro it 100% of the time with ONE instance.

[hannesrudolph]

@privacyguy123 are there any other vs code instances open at the time of these rogue processes?

No, or else I wouldn't have said "after VSCode is completely closed." I can repro it 100% of the time with ONE instance.

if it was clear I would not have said `"@privacyguy123 are there any other vs code instances open at the time of these rogue processes?"

[privacyguy123]

I think I should mention the commit linked to this issue did not fix the issue.

[robertheadley]

I have previously noticed this as well.

[hannesrudolph]

@xyOz-dev think this lends to the grey screens?