How to Properly Release Resources in Viser Server?

[MarjordCpz]

Hi, thanks for your fantastic visualizer!

I have encountered a problem while using Viser and would greatly appreciate your guidance. Thank you in advance for taking the time to help me—I truly value your support.

Problem description
I am currently using Viser in Gradio, and the overall implementation logic is as follows:

• There is a button for switching data. When clicking the button, the reset method (scene.reset()) is called to reset the scene and load the next file.

But I found that as the number of loaded files increases, the memory usage of the task will continue to increase, and the resources of the previous scene cannot be effectively released.

My needs
Before loading a new scene, is there a way to completely release the memory resources of the previous scene to avoid the problem of increasing memory usage?
If Viser has a recommended method or related API, I hope to get some guidance.

Thank you for your help!

[brentyi]

Hi there!

There are some known issues here, which I addressed in #353. If that doesn't fix it and you have a runnable example I'm happy to investigate further!

[MarjordCpz]

@brentyi
Thank you so much for your prompt reply and assistance! I will give it a try within the next two days. My current workaround is not ideal—I wrote an additional script to monitor the Viser script and automatically restart it if it exceeds a certain threshold. At least it’s functioning for now.
If I encounter any further issues, I will provide timely feedback and runnable example. Once again, I greatly appreciate your help!