Absurd amount of cpu and memory usage when doing pah completion
Its kind of like a forkbomb, I am using github copilot and cpu goes 100% and same for memory, i typed .local/share and its going flames. On latest.
this happens to me as well but only when in my ~home directory. probably just because of the massive number of files and folders it has to search through
this happens to me as well but only when in my ~home directory. probably just because of the massive number of files and folders it has to search through
Yeah true. Though fzf can do it.
+1, I Open on home directory and type @ and it goes off
[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
Yep still needed @rekram1-node
Maybe skim can help? Fzf takes a lot of ram. Also other ways can be taken other than using fzf or similar. I think fzf indexes from start on each run. Instead, opencode should maintain a index in the background. This will dramatically decrease ram usage on future runs (first runs will be slow, starting from 0)
what version are you using?
I don't think we use fzf anymore
@MuntasirSZN
what version are you using?
I don't think we use fzf anymore
@MuntasirSZN
Latest always... Idk but it may not be fzf anymore, I just looked at internals one day and never rechecked it. Though the issue persists.
related: https://github.com/sst/opencode/issues/2585 seems opencode never releases large files read in memory
and u get this issue specifically with “@“? Because otherwise ill close we have a lot of related issues and this one is older
I don't have very large files in home dir, they are in hidden dirs like local or cache. I have a lot of small files, that can be said.
But is it specifically hapening when you open the "@" completions bar in the tui?
But is it specifically hapening when you open the "@" completions bar in the tui?
Yes, specially in really large folders like home dir.