anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Massive memory use on opening opencode when there is a very large file #1709

New Issue
Open
opened 2026-02-16 17:32:16 -05:00 by yindo · 12 comments
yindo commented 2026-02-16 17:32:16 -05:00
Owner
Copy Link
Copy Source

Originally created by @TimAidley on GitHub (Sep 13, 2025).

Originally assigned to: @thdxr on GitHub.

Before trying out opencode, I had been experimenting which chunkhound, that indexes your source folder to allow searching later. It stores its database file(s) in the .chunkhound folder, and in my project that folder was around 27GB in size.

It seems like opencode was trying to load the files in that folder, because when I ran opencode the memory usage would shoot up, and opencode was using 29GB of RAM, and my computer was getting very slow.

Deleting that folder solved the problem. Unfortunately I didn't check what the sizes and filetypes of files in that folder were before I deleted it.

Originally created by @TimAidley on GitHub (Sep 13, 2025). Originally assigned to: @thdxr on GitHub. Before trying out opencode, I had been experimenting which chunkhound, that indexes your source folder to allow searching later. It stores its database file(s) in the `.chunkhound` folder, and in my project that folder was around 27GB in size. It seems like opencode was trying to load the files in that folder, because when I ran opencode the memory usage would shoot up, and opencode was using 29GB of RAM, and my computer was getting very slow. Deleting that folder solved the problem. Unfortunately I didn't check what the sizes and filetypes of files in that folder were before I deleted it.
yindo commented 2026-02-16 17:32:16 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Sep 13, 2025):

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

  • #683: Hangs if there is a multi gb .tar.gz file in current directory - similar issue with large files causing hangs
  • #1126: Session grew to 88G! - another case of extreme memory usage
  • #2262: Running opencode causes a git diff that consumes all memory - similar memory consumption issue resolved by removing large files
  • #804: URGENT - "MEM LEAK", eats up gigabytes of ram until system crash - memory leak issue with large files

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

@github-actions[bot] commented on GitHub (Sep 13, 2025): This issue might be a duplicate of existing issues. Please check: - #683: Hangs if there is a multi gb .tar.gz file in current directory - similar issue with large files causing hangs - #1126: Session grew to 88G! - another case of extreme memory usage - #2262: Running opencode causes a git diff that consumes all memory - similar memory consumption issue resolved by removing large files - #804: URGENT - "MEM LEAK", eats up gigabytes of ram until system crash - memory leak issue with large files Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:32:16 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Sep 13, 2025):

good to know thx for raising

@rekram1-node commented on GitHub (Sep 13, 2025): good to know thx for raising
yindo commented 2026-02-16 17:32:16 -05:00
Author
Owner
Copy Link
Copy Source

@zelenkovsky commented on GitHub (Sep 22, 2025):

In my case, it's 72GB of memory that got committed right after start (for other repository it's 93GB):

Image
@zelenkovsky commented on GitHub (Sep 22, 2025): In my case, it's 72GB of memory that got committed right after start (for other repository it's 93GB): <img width="856" height="599" alt="Image" src="https://github.com/user-attachments/assets/7c2e72cc-fdb5-4aeb-b517-d0f68c514574" />
yindo commented 2026-02-16 17:32:17 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Sep 22, 2025):

@zelenkovsky can you tell me more about where you are running opencode is this a massive project or something?

@rekram1-node commented on GitHub (Sep 22, 2025): @zelenkovsky can you tell me more about where you are running opencode is this a massive project or something?
yindo commented 2026-02-16 17:32:17 -05:00
Author
Owner
Copy Link
Copy Source

@zelenkovsky commented on GitHub (Sep 24, 2025):

@rekram1-node, aha, very interesting thing. If my working folder has a backup subfolder with large .tar.gz files, the opencode executable starts to grow in size (virtual memory) and gets killed by the OOM Killer.

Is there anything special in backup or tar.gz handling?

That happens on application startup. I did not even enter anything.

@zelenkovsky commented on GitHub (Sep 24, 2025): @rekram1-node, aha, very interesting thing. If my working folder has a `backup` subfolder with large .tar.gz files, the `opencode` executable starts to grow in size (virtual memory) and gets killed by the OOM Killer. Is there anything special in `backup` or `tar.gz` handling? That happens on application startup. I did not even enter anything.
yindo commented 2026-02-16 17:32:17 -05:00
Author
Owner
Copy Link
Copy Source

@zelenkovsky commented on GitHub (Sep 24, 2025):

Actually, backup has nothing to do with it; it's large tar.gz files located anywhere in the project folder.

@zelenkovsky commented on GitHub (Sep 24, 2025): Actually, `backup` has nothing to do with it; it's large `tar.gz` files located anywhere in the project folder.
yindo commented 2026-02-16 17:32:17 -05:00
Author
Owner
Copy Link
Copy Source

@zelenkovsky commented on GitHub (Sep 24, 2025):

Analysis Summary

I've identified the root cause of the high virtual memory consumption when large .tar.gz files are present in your working directory. Here's what happens during opencode startup:

Primary Issue: File Tree Generation at Startup

  1. Location: packages/opencode/src/session/system.ts:47-50
  2. Function: SystemPrompt.environment() calls Ripgrep.tree() during initialization
  3. Process: This scans ALL files in your project directory to build a project tree structure that gets included in the system prompt

The Problem Chain:

  1. File Scanning: Ripgrep.tree() → Ripgrep.files() → ripgrep binary with --files flag
  2. No Archive Filtering: The default ignore patterns in FileIgnore don't include common archive extensions like *.tar.gz, *.zip, *.tar, etc.
  3. Memory Allocation: When ripgrep encounters large files (even if it's just listing them), it can cause memory allocation issues, especially with compressed archives
  4. Startup Execution: This happens before any conversation starts, during the system prompt preparation

Evidence from Code:

• src/session/system.ts:47-50: Calls Ripgrep.tree() with limit of 200 files during environment setup
• src/file/ignore.ts: Missing patterns for archive files (*.tar.gz, *.zip, *.tar, *.7z, etc.)
• src/file/ripgrep.ts:206-220: The files() function uses ripgrep's --files flag which scans the entire directory

Verification Checklist: ✅ Verified: File scanning occurs at startup via SystemPrompt.environment() ✅ Verified: No archive file patterns in default ignore list ✅ Verified: Ripgrep.files() scans
entire directory structure ❓ Inferred: Large archive files cause memory allocation during scanning

Next Steps to Confirm: You could verify this by temporarily moving your .tar.gz files out of the working directory and checking if the memory usage drops during opencode startup.

The fix would involve adding archive file patterns to the default ignore list in src/file/ignore.ts.

@zelenkovsky commented on GitHub (Sep 24, 2025): ## Analysis Summary I've identified the root cause of the high virtual memory consumption when large .tar.gz files are present in your working directory. Here's what happens during opencode startup: Primary Issue: File Tree Generation at Startup 1. Location: packages/opencode/src/session/system.ts:47-50 2. Function: SystemPrompt.environment() calls Ripgrep.tree() during initialization 3. Process: This scans ALL files in your project directory to build a project tree structure that gets included in the system prompt The Problem Chain: 1. File Scanning: Ripgrep.tree() → Ripgrep.files() → ripgrep binary with --files flag 2. No Archive Filtering: The default ignore patterns in FileIgnore don't include common archive extensions like *.tar.gz, *.zip, *.tar, etc. 3. Memory Allocation: When ripgrep encounters large files (even if it's just listing them), it can cause memory allocation issues, especially with compressed archives 4. Startup Execution: This happens before any conversation starts, during the system prompt preparation Evidence from Code: • src/session/system.ts:47-50: Calls Ripgrep.tree() with limit of 200 files during environment setup • src/file/ignore.ts: Missing patterns for archive files (*.tar.gz, *.zip, *.tar, *.7z, etc.) • src/file/ripgrep.ts:206-220: The files() function uses ripgrep's --files flag which scans the entire directory Verification Checklist: ✅ Verified: File scanning occurs at startup via SystemPrompt.environment() ✅ Verified: No archive file patterns in default ignore list ✅ Verified: Ripgrep.files() scans entire directory structure ❓ Inferred: Large archive files cause memory allocation during scanning Next Steps to Confirm: You could verify this by temporarily moving your .tar.gz files out of the working directory and checking if the memory usage drops during opencode startup. The fix would involve adding archive file patterns to the default ignore list in src/file/ignore.ts.
yindo commented 2026-02-16 17:32:17 -05:00
Author
Owner
Copy Link
Copy Source

@ofriw commented on GitHub (Sep 28, 2025):

Before trying out opencode, I had been experimenting which chunkhound, that indexes your source folder to allow searching later. It stores its database file(s) in the .chunkhound folder, and in my project that folder was around 27GB in size.

It seems like opencode was trying to load the files in that folder, because when I ran opencode the memory usage would shoot up, and opencode was using 29GB of RAM, and my computer was getting very slow.

Deleting that folder solved the problem. Unfortunately I didn't check what the sizes and filetypes of files in that folder were before I deleted it.

Author of ChunkHound here. As a workaround, you can place the db file outside of your code's dir using the --db flag. See https://chunkhound.github.io/configuration/#database-options

@ofriw commented on GitHub (Sep 28, 2025): > Before trying out opencode, I had been experimenting which chunkhound, that indexes your source folder to allow searching later. It stores its database file(s) in the `.chunkhound` folder, and in my project that folder was around 27GB in size. > > It seems like opencode was trying to load the files in that folder, because when I ran opencode the memory usage would shoot up, and opencode was using 29GB of RAM, and my computer was getting very slow. > > Deleting that folder solved the problem. Unfortunately I didn't check what the sizes and filetypes of files in that folder were before I deleted it. Author of ChunkHound here. As a workaround, you can place the db file outside of your code's dir using the `--db` flag. See https://chunkhound.github.io/configuration/#database-options
yindo commented 2026-02-16 17:32:17 -05:00
Author
Owner
Copy Link
Copy Source

@IlyaMaksheev commented on GitHub (Oct 2, 2025):

I also experience same issue with .parquet files.

@IlyaMaksheev commented on GitHub (Oct 2, 2025): I also experience same issue with `.parquet` files.
yindo commented 2026-02-16 17:32:17 -05:00
Author
Owner
Copy Link
Copy Source

@scarf005 commented on GitHub (Dec 25, 2025):

hi @rekram1-node, could https://github.com/sst/opencode/pull/2761 be taken a look? also getting 17GiB ram usage on repository with lots of image files

@scarf005 commented on GitHub (Dec 25, 2025): hi @rekram1-node, could https://github.com/sst/opencode/pull/2761 be taken a look? also getting 17GiB ram usage on repository with lots of image files
yindo commented 2026-02-16 17:32:17 -05:00
Author
Owner
Copy Link
Copy Source

@SPOOKEXE commented on GitHub (Jan 4, 2026):

Its reading my .venv folder as well, or there is something stored in session histories. I've been sitting at 5GB, but have been to 20GB+. Could we get a panel that displays a breakdown of memory usage, or some instructions on how to view what consumes it?

@SPOOKEXE commented on GitHub (Jan 4, 2026): Its reading my .venv folder as well, or there is something stored in session histories. I've been sitting at 5GB, but have been to 20GB+. Could we get a panel that displays a breakdown of memory usage, or some instructions on how to view what consumes it?
yindo commented 2026-02-16 17:32:17 -05:00
Author
Owner
Copy Link
Copy Source

@aniel300 commented on GitHub (Jan 21, 2026):

same issue

@aniel300 commented on GitHub (Jan 21, 2026): same issue
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1709
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?