Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[framework] AgentFabric local deploy has memory leak #435

Open
3 tasks done
fire7night opened this issue May 11, 2024 · 1 comment
Open
3 tasks done

[framework] AgentFabric local deploy has memory leak #435

fire7night opened this issue May 11, 2024 · 1 comment
Assignees
Labels
agentfabric issues with agentfabric bug Something isn't working framework any issues with the modelscope-agent framework misfunction

Comments

@fire7night
Copy link

Initial Checks

  • I have searched GitHub for a duplicate issue and I'm sure this is something new
  • I have read and followed the docs & demos and still think this is a bug
  • I am confident that the issue is with modelscope-agent (not my code, or another library in the ecosystem)

What happened + What you expected to happen

I deploy the apps/agentfabric in local. The entire deployment process is successful.
But when we visit the web page, the system memory of the Python process will continue to rise and will not fall.
Memory rise occurs when the new visits/refresh the tab pages.
The memory use after a period of time is as follows:
图片

How to solve this problem?🤔

Versions / Dependencies

base on conda
python: 3.10
os: Linux centos / macos(docker fedora40) ((we both tried))
cuda: Linux centos:11.7 / macos:None
torch: Linux(torch==2.0.1 torchvision==0.15.2 torchaudio==2.0.2) / macos(torch==2.2.2 torchvision==0.17.2 torchaudio==2.2.2 cpu)
both requirements.txt has been installed.
git branch: master

Reproduction script

None

Issue Severity

High: It blocks me from completing my task.

@fire7night fire7night added the bug Something isn't working label May 11, 2024
@zzhangpurdue
Copy link
Collaborator

This is a known issue, it is aleady on our todo list.
Since you mentioned this problem, we will put it in a high priority, and fix this problem in next release.

The main reason for this issue, is the agent is not fully gc, so each time a new agent instantiated it will consume memory, and when you leave, it is still hold the memory.

@zzhangpurdue zzhangpurdue added agentfabric issues with agentfabric framework any issues with the modelscope-agent framework misfunction labels May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agentfabric issues with agentfabric bug Something isn't working framework any issues with the modelscope-agent framework misfunction
Projects
None yet
Development

No branches or pull requests

3 participants