[bug] open-local agent may have memory leak
- Dominant language
- Go
- Stars
- 515
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
### Ⅰ. Issue Description
```bash
yoda-agent-z4kts 39m 208Mi
yoda-agent-48nqc 42m 192Mi
yoda-agent-zmgxz 50m 190Mi
yoda-agent-8r7vq 38m 181Mi
yoda-agent-5lbnj 37m 175Mi
yoda-agent-42xqb 47m 102Mi
yoda-agent-hrj5g 59m 84Mi
yoda-agent-89glg 59m 77Mi
yoda-agent-brzpb 51m 53Mi
```
It is weird that open-local agent uses so much memory(about 200Mi).
### Ⅱ. Describe what happened
It may be difficult to troubleshoot because there is no more information.
Contributor guide
No contributing guide indexed for this repository
Research direction
The report names no files, tests, or entry points and provides only pod memory samples. Start by reproducing the open-local agent's memory growth under the same workload, then trace the relevant Go agent component. Done means the leak is identified and fixed, with evidence that comparable agents no longer grow to this level.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100