Skip to content

Serious memory leak on the Windows platform #10248

Closed
Closed
Serious memory leak on the Windows platform#10248
Assignees
rekram1-node
Labels
bugSomething isn't workingperfIndicates a performance issue or need for optimizationwindows

Description

@jsrcode
jsrcode
opened on Jan 23, 2026

Description

Serious memory leak on the Windows platform
Operating system: Windows 11 24H2
OpenCode version: 1.1.34
This happens many times in a row and eats up all the remaining memory of the system, causing the CLI to crash
I have observed that the OpenCode memory usage is 12G in the task manager
Total device memory: 128G

Plugins

"oh-my-opencode",     "@tarquinen/opencode-dcp@latest",     "opencode-omit-max-tokens"

OpenCode version

1.1.34

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

Windows 11 24H2

Terminal

Windows Terminal

Activity

  1. jsrcode
    added
    bugSomething isn't working
    on Jan 23, 2026
  2. github-actions
    assigned
    rekram1-node
    on Jan 23, 2026
  3. github-actions
    added
    perfIndicates a performance issue or need for optimization
    windows
    on Jan 23, 2026

  4. github-actions commented on Jan 23, 2026

    @github-actions
    github-actionsBot
    on Jan 23, 2026 – with GitHub Actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    Feel free to ignore if none of these address your specific case.

  5. jsrcode commented on Jan 23, 2026

    @jsrcode
    jsrcode
    on Jan 23, 2026
    Author
    Image In the normal state, it also eats two Gs, which is too exaggerated

  6. jsrcode commented on Jan 23, 2026

    @jsrcode
    jsrcode
    on Jan 23, 2026
    Author
    Image After just 6 minutes of running he already has 2GB more memory

  7. jsrcode commented on Jan 23, 2026

    @jsrcode
    jsrcode
    on Jan 23, 2026
    Author
    Image This is after 19 minutes of operation already reaches 7GB, close to 8GB

  8. jsrcode commented on Jan 23, 2026

    @jsrcode
    jsrcode
    on Jan 23, 2026
    Author
    Image oh no. After twenty minutes, the memory has reached a terrifying 8GB.

  9. jsrcode commented on Jan 23, 2026

    @jsrcode
    jsrcode
    on Jan 23, 2026
    Author
    Image 29 minutes 10GB

  10. jsrcode commented on Jan 23, 2026

    @jsrcode
    jsrcode
    on Jan 23, 2026
    Author
    Image This was after 34 minutes of running and he was really bad that he would crash my computer and my games and other software clients hanging in the background had crashed many times by him

  11. jsrcode commented on Jan 23, 2026

    @jsrcode
    jsrcode
    on Jan 23, 2026
    Author
    Image After 47 minutes of running 12GB of RAM has been eaten
  12. cristian1991
    added a commit that references this issue on Jan 24, 2026

    feat(desktop): add hardware acceleration toggle for Windows

    1491dc5

  13. tskimmett commented on Feb 13, 2026

    @tskimmett
    tskimmett
    on Feb 13, 2026

    Yep, uses way too much memory.

  14. thdxr commented on Apr 2, 2026

    @thdxr
    thdxr
    on Apr 2, 2026
    Member

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

  15. thdxr
    closed this as completedon Apr 2, 2026
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 optimizationwindows

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions