-
Notifications
You must be signed in to change notification settings - Fork 106
Potential memory leak on Maniskill3? #87
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
Comments
Could try running
And what other code are you running besides the environment? |
And what version of maniskill 3 is being used? git? pypi? nightly? |
Hi Stone! Thanks for the reply. Yes, I did include gc in my code, and that doesn't change the result, which surprises me The maniskill3 version I was using is 3.0.0b20. I don't quite remember how I installed it tho, sorry. The code I was running works like this. On the websocket client side, an evaluator object is spawned and queries Simpler/Maniskill3 to get images and robot states. It then packs this data to send to a websocket server The server is simply a VLA model that accepts input, generates actions, and sends them back to the client/evaluator to execute. Currently, all things run on one single machine, but the architecture is written so that in the future I can run inference separately from the robot. The code looks like this
|
I see. Could you try pip uninstall maniskill and then install mani-skill-nightly? |
Thanks. I will report back when I get home and have time to test. For the time being I am using multi-processing to speed up ms2-based simpler |
Hi!
Thanks for open-sourcing this awesome project.
Recently, I switched to the maniskill3 branch, and I noticed that I have been getting OOM issues if I switch between too many envs.
My workflow is roughly as follows:
I make env A, do some parallel testing, make sure to close and delete this env by calling
env.close()
anddel env
, and make env B, rinse and repeat. All in a single process.But I noticed that the VRAM does not drop when an env is closed.
I double-checked the time, and the time at which VRAM increases is indeed the time a new env is made.
The specific error message I got is this
I came across this issue on Maniskill's main repo, but it seems like the API to manually clear the assets is no longer in the codebase anymore
The text was updated successfully, but these errors were encountered: