You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
PyCharm 2026.2 AI Assistant spawns 15-22 opencode.exe acp processes on startup, causing memory exhaustion and crash (0xC0000409) #40693
When PyCharm 2026.2 starts with the AI Assistant configured to use opencode as an ACP provider, the AI Assistant bulk-creates 15-22 chat sessions during IDE initialization. Each session independently spawns a separate opencode.exe acp process, and each process goes through full initialization (model loading, MCP server connections, etc.). This causes memory usage to spike to 100%, eventually crashing PyCharm with exit code 0xC0000409 (STATUS_STACK_BUFFER_OVERRUN).
The following workarounds are NOT acceptable:
Disabling JetBrains Client Protocol (JCP)
Uninstalling the ml-llm plugin
Requirement: keep opencode usable inside the IDE via AI Assistant's ACP integration, while preventing the startup-time chat/process explosion.
Plugins
JetBrains AI Assistant (bundled with PyCharm 2026.2) - opencode ACP integration (configured as AI Assistant ACP provider)
OpenCode version
1.18.12
Steps to reproduce
Install PyCharm 2026.2, configure AI Assistant to use opencode as ACP provider
Start PyCharm
Observe in Task Manager: opencode.exe acp process count rapidly grows from 0 to 15-22
If your issue is specifically about ACP bulk-creating sessions during PyCharm IDE initialization triggering the process explosion, it may be a distinct root cause worth keeping separate. But please review the above issues first to see if they cover your scenario.
Activity
github-actions commentedon Aug 5, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is specifically about ACP bulk-creating sessions during PyCharm IDE initialization triggering the process explosion, it may be a distinct root cause worth keeping separate. But please review the above issues first to see if they cover your scenario.