OpenTUI causes crashes and heavy memory usage #3798

Activity

1. yudgnahk

   added

   bugSomething isn't workingSomething isn't working

   on Nov 3, 2025
2. github-actions

   added

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   on Nov 3, 2025
3. github-actions commented on Nov 3, 2025

   

   github-actionsBot

   on Nov 3, 2025 – with GitHub Actions

   Contributor

   More actions

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

   • Uses a huge amount of memory #3013: Reports huge memory usage that keeps increasing until opencode gets stuck during extensive AI sessions
   • High RAM usage in latest release #2805: High RAM usage in latest release, specifically tied to Bun processes
   • Massive memory use on opening opencode when there is a very large file #2585: Massive memory use (29GB reported) when opencode tries to load large files
   • [BUG] Unable to Load Old Sessions #3669: Unable to load old sessions, conversation history flashes and disappears (similar session loading issues)
   • Deleted a few sessions and now opencode crashes on prompt #1215: Crashes on prompt after deleting sessions, with session-related memory access errors

   Feel free to ignore if none of these address your specific case.
4. yudgnahk commented on Nov 3, 2025

   

   yudgnahk

   on Nov 3, 2025

   ContributorAuthor

   More actions

   Load this session:
   

   Session not found:
   

   Then crash when I load again:
   
5. yudgnahk commented on Nov 3, 2025

   

   yudgnahk

   on Nov 3, 2025

   ContributorAuthor

   More actions

   Another session loading with black screen only, loading forever.

   
6. rekram1-node commented on Nov 3, 2025

   

   rekram1-node

   on Nov 3, 2025

   Contributor

   More actions

   Is this because of opentui? Or is it because you made a giant session to test the limits of session lists and performance there? Does this session work fine on old opencode?

   I know u have a PR with the diff stuff and Ill take a look but to help us narrow down for the time being these may be good questions to know answers to
7. yudgnahk commented on Nov 3, 2025

   

   yudgnahk

   on Nov 3, 2025

   ContributorAuthor

   More actions

   @rekram1-node honestly, I don't know the reason why. I can get the session list immediately with the current opencode version.

   With the old version (before v1.0.0):

   • Get list session: slow (~10 seconds).
   • Session detail: work well.

   With new new version (v1.0.15):

   • Get list session: fast
   • Session detail: not working well.
     • Can't get one of my latest session: don't know why => just black screen. The session is described below:

   {
     "id": "ses_5c44fd2d3ffepRC82zPWENtICF",
     "version": "0.15.30",
     "projectID": "598a424a62b89b2f7a5ba86dfcccd507051ab377",
     "directory": "/home/khanghld27/big_file_reader",
     "title": "Investigating 500MB file server crash",
     "time": {
       "created": 1761937993004,
       "updated": 1761994168699
     },
     "summary": {
       "diffs": []
     }
   }
   

   • I just started a new session, ask it to look for the session directory, to investigate why I can't log that session. The session is described below:

   {
     "id": "ses_5b7d0873fffeYprN0gfMLnPi6P",
     "version": "1.0.15",
     "projectID": "598a424a62b89b2f7a5ba86dfcccd507051ab377",
     "directory": "/home/khanghld27/big_file_reader",
     "title": "Investigating session freeze in opencode",
     "time": {
       "created": 1762147662016,
       "updated": 1762147817910
     },
     "summary": {
       "diffs": []
     }
   }
   

   • Then while the opencode was working, it became frozen. I checked the memory usage, it went to 14GB for opencode. Then I stopped the opencode, then opened it again, trying to load the last session, and got the crash.

   If you need anything else, please let me know.
8. rekram1-node commented on Nov 3, 2025

   

   rekram1-node

   on Nov 3, 2025

   Last edited by rekram1-node

   Contributor

   More actions

   Ah the blank screen is some rendering bug I think, some people said they can scroll to it but yeah needs to be fixed

   thanks for the details we will address this!
9. jerome-benoit commented on Nov 3, 2025

   

   jerome-benoit

   on Nov 3, 2025

   Last edited by jerome-benoit

   Contributor

   More actions

   Bitten by similar issue.

   To reproduce with 1.0.15:

   • checkout https://github.com/poolifier/poolifier
   • start opencode in the repo
   • prompt with something like: "run the tinybench benchmarks and analyze the results"
   • watch opencode/opentui memory usage grows up to several Go, freeze, your computer being not responsive and the OS OOM killer kill opencode.

   And yes, it was working before the version 1.

   👍React with 👍4Reacted by Khang Ha (Kelvin), Ben Girard, Rajesh Rajendran and cureforpain
10. rekram1-node commented on Nov 3, 2025

    

    rekram1-node

    on Nov 3, 2025

    Last edited by rekram1-node

    Contributor

    More actions

    OO okay that's really helpful ty @jerome-benoit
11. thdxr

    assigned

    kommander

    on Nov 4, 2025
12. thdxr commented on Nov 6, 2025

    

    thdxr

    on Nov 6, 2025 – with Linear

    Member

    More actions

    can you try again with latest?
13. rjshrjndrn commented on Nov 6, 2025

    

    rjshrjndrn

    on Nov 6, 2025

    More actions

    The new UI is taking around ~30% consistently to analyze a small code base while old v0.15.31 starts with a spike 50 and then uses around ~7-11%.
    Checked with the latest version.
14. kommander commented on Nov 12, 2025

    

    kommander

    on Nov 12, 2025 – with Linear

    Contributor

    More actions

    A lot of improvements went into the latest versions, is this one any better?
15. kommander

    closed this as completedon Dec 20, 2025