MoonshotAI / MoonshotAI/kimi-code
存在内存泄露问题
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
What version of Kimi Code is running?
0.14.3
Which open platform/subscription were you using?
Kimi Code (OAuth)
Which model were you using?
kimi-for-coding
What platform is your computer?
Linux 7.0.11-locietta-WSL2-xanmod1 x86_64 unknown
What issue are you seeing?
同时开启3个 kimi code 对三个项目进行开发，运行差不多一个小时后，系统内存占用能从一开始的 66% 上升至 95%，并且把三个 kimi code 都 exit 后，内存就回到原来的水平了。
What steps can reproduce the bug?
- 同时开启3个 kimi code 对三个项目进行正常开发
- 运行大概一个小时后，系统内存占用能从一开始的 66% 飙升至 95%
- 把三个 kimi code 都 exit 后，内存占用就回到原来的水平。
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. First reproduce the report with three Kimi Code 0.14.3 instances on the stated Linux WSL2 environment, using the kimi-for-coding model and OAuth, while monitoring memory for about an hour. Trace which process resources grow and verify that normal use no longer causes the reported increase toward 95%.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100