Skip to content

OpenChamber spawning multiple processes causing high CPU usage #38489

Closed as not planned

Description

@Doinkydoink

Description

Version: 1.18.4
Description: Multiple openchamber serve processes running simultaneously, causing 80%+ CPU usage
Process info:
PID 95398: 87.6% CPU
PID 95436: 69.6% CPU
PID 95477: 40.0% CPU
Expected: Single OpenChamber process with minimal CPU usage
Actual: Multiple processes spawning, high CPU load (7+ load average)

Plugins

No response

OpenCode version

1.18.4

Steps to reproduce

Version: 1.18.4 Interface: OpenChamber Update Policy: bundled

Description: OpenChamber is spawning multiple serve processes simultaneously, causing excessive CPU usage (80%+ per process, load average 7+).

Process Information:
PID 95398: 87.6% CPU - node /usr/local/bin/openchamber serve --foreground --port 3010 --host 127.0.0.1
PID 95436: 69.6% CPU - node /usr/local/bin/openchamber serve --foreground --port 3010 --host 127.0.0.1
PID 95477: 40.0% CPU - node /usr/local/bin/openchamber serve --foreground --port 3010 --host 127.0.0.1
PID 55254: 0.9% CPU - node /usr/local/bin/openchamber-ingress-proxy.js
PID 375: 3.3% CPU - node /usr/local/bin/openchamber serve (earlier instance)
Expected Behavior: Single OpenChamber process with minimal CPU usage when idle

Actual Behavior: Multiple openchamber serve processes spawning, causing:

80%+ CPU usage per process
Load average 7+ on the system
System resources exhausted
Environment:

Home Assistant OS
OpenCode add-on v1.18.4
No custom plugins installed
MCP servers: homeassistant (enabled), homeassistant_native (disabled)
LSP: ha-yaml
Formatter: prettier
Additional Context:

CPU usage spikes when OpenChamber is active

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Activity

  1. btriapitsyn commented on Aug 29, 2026

    @btriapitsyn

    Why it was posted here? Create a proper issue in https://github.com/openchamber/openchamber/issues

    @rekram1-node, sorry for that, please close this.

  2. thdxr commented on Oct 11, 2026

    @thdxr
    Member

    Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.

    — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions