[BUG] VSCode: closing chat tab does not terminate ACP child process, causing orphan processes

[zhangxy-zju]

What happened?

When using the Qwen Code VSCode extension, closing a chat tab (either the editor panel or the sidebar view) leaves the ACP CLI child process running as an orphan. The process persists indefinitely until VSCode is fully quit or the process is manually killed.

Steps to reproduce:

1. Open VSCode with the Qwen Code extension installed
2. Open a Qwen Code chat tab
3. Verify CLI process is running: ps aux | grep -E 'qwen.*acp.*VSCode' | grep -v grep
4. Close the chat tab
5. Check again — the CLI process is still running

With heavy usage (multiple tabs, frequent open/close), orphan processes accumulate.

Root cause

WebViewProvider's panel onDidDispose and sidebar view onDidDispose callbacks do not call agentManager.disconnect(). Only WebViewProvider.dispose() (triggered on extension deactivation) has the disconnect call. Closing a tab triggers onDidDispose on the panel/view, not WebViewProvider.dispose(), so the CLI child process never receives SIGTERM.

What did you expect to happen?

Closing the chat tab should terminate the associated CLI child process.

Client information

• VSCode extension version: 0.13.0
• OS: macOS (darwin arm64)

[pomelo-nwu]

感谢反馈！这个问题确实是资源泄漏，需要修复。

问题根因分析：
关闭聊天标签页时，ACP CLI 子进程没有被正确终止。可能原因：

• VSCode 扩展在面板关闭时未调用清理逻辑
• ACP 客户端断开连接后，子进程未收到终止信号

建议修复方案：

1. 监听 / 事件，检测标签页关闭
2. 在扩展的 中确保 terminate 所有 ACP 子进程
3. 使用 并设置超时强制 kill

我来帮忙定位具体代码并修复这个问题。