Skip to content

Version 1.2.18 of Windows has a bug with memory leaks, causing extremely high CPU usage!!! #16250

Closed

Description

@yourfei

Description

The memory usage in this version has exceeded 30 GB, and the CPU usage of msedgewebview2.exe once reached over 50%. Please look into it.

Plugins

nothing

OpenCode version

1.2.18

Steps to reproduce

During normal code writing

Screenshot and/or share link

Image

Operating System

windows 10 21H2

Terminal

bash

Activity

  1. added
    perfIndicates a performance issue or need for optimization
    webRelates to opencode on web / desktop
    needs:complianceThis means the issue will auto-close after 2 hours.
    and removed
    needs:complianceThis means the issue will auto-close after 2 hours.
    on Mar 6, 2026
  2. github-actions commented on Mar 6, 2026

    @github-actions
    Contributor

    Thanks for updating the issue! It now includes a clear description, reproduction context, a screenshot, and system information. Everything looks good — the compliance flag has been removed.

  3. moonray commented on Mar 6, 2026

    @moonray

    The mac version seems to have memory leaks as well. Starting a new session from within OpenCode with /new doesn't clear the memory use. Only way is to quite and then resume.

    Image
  4. Zjemm commented on Mar 6, 2026

    @Zjemm

    runnin on ubuntu same issue's. constant out of memory and crash

  5. blaze6950 commented on Mar 7, 2026

    @blaze6950

    I have a similar issue on Windows 10 Professional: the Bun process's CPU usage sometimes (during the build agent's execution) reaches 60+%. Memory usage is around 1 GB.

    Opencode TUI version: 1.2.20
    RAM: 16 GB
    CPU: Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz

    P.S. In a previous version, I didn't notice high CPU usage, so the issue is quite fresh.

  6. cloudmidleman commented on Mar 15, 2026

    @cloudmidleman

    1371113 opencode 20 0 79.9g 5.1g 59652 S 175.0 10.8 63:47.34 opencode

  7. thdxr commented on Apr 2, 2026

    @thdxr
    Member

    Closing in favor of #20695 where we're collecting all memory-related problems. Please follow that issue for updates.

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

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingperfIndicates a performance issue or need for optimizationwebRelates to opencode on web / desktopwindows

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions