High memory usage #6571

Activity

1. ravshansbox

   added

   bugSomething isn't workingSomething isn't working

   on Jan 1, 2026
2. github-actions

   assigned

   rekram1-node

   on Jan 1, 2026
3. github-actions

   added

   perfIndicates a performance issue or need for optimizationIndicates a performance issue or need for optimization

   on Jan 1, 2026
4. github-actions commented on Jan 1, 2026

   

   github-actionsBot

   on Jan 1, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Too high memory usage #5700: Too high memory usage
   • opencode eating 70gb of memory? #5363: opencode eating 70gb of memory?
   • Multiple instances occupy a large amount of memory #6058: Multiple instances occupy a large amount of memory
   • Single opencode session is consuming 23+GB of memory #3995: Single opencode session is consuming 23+GB of memory

   Feel free to ignore if none of these address your specific case.
5. rekram1-node commented on Jan 1, 2026

   

   rekram1-node

   on Jan 1, 2026

   Last edited by rekram1-node

   Contributor

   More actions

   @ravshansbox your opencode version doesnt exist
6. ravshansbox commented on Jan 2, 2026

   

   ravshansbox

   on Jan 2, 2026

   ContributorAuthor

   More actions

   @rekram1-node sorry, it was 1.0.218
7. capoBrandelli commented on Jan 2, 2026

   

   capoBrandelli

   on Jan 2, 2026

   More actions

   Memory spikes >80GB here - on a project with 1.3 GB of data. Kills the session and sometimes the server (current opencode 1.0.223). Thanks for the otherwise fantastic platform!
8. rekram1-node commented on Jan 2, 2026

   

   rekram1-node

   on Jan 2, 2026

   Contributor

   More actions

   I think we found some issues that could be causing this, should be addressed soon

   👍React with 👍3Reacted by liamfogarty10, ravshansbox and capoBrandelli
9. rekram1-node

   closed this as duplicateon Jan 2, 2026
10. rekram1-node

    reopened this on Jan 2, 2026
11. rekram1-node

    closed this as duplicateon Jan 2, 2026
12. ravshansbox commented on Jan 2, 2026

    

    ravshansbox

    on Jan 2, 2026

    ContributorAuthor

    More actions

    @rekram1-node which ticket tracks this issue?
13. tadghh commented on Jan 4, 2026

    

    tadghh

    on Jan 4, 2026

    More actions

    Still an issue on 1.0.203