You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently using monst3r by repetitively reconstructing 3D point clouds for a series of videos.
However, I observed that there is a GPU memory leakage, where the GPU memory gradually increases and finally the CUDA OOM error occurs after handling several dozens of images.
I've tried to delete the 'scene' variable memory by inserting del scene after global_alignment, but it doesn't address the issue.
Can you help me to address this GPU memory leakage issue?
Thank you in advance.
The text was updated successfully, but these errors were encountered:
Thanks for the feedback. Could you please elaborate more on the issue? For example, is it possible for you to process the longest video of your series? Also, if you are encountering the issue when using demo.py, you could probably try to use or refer to pose_eval.py, which may help avoid this problem.
Actually, I made a custom function as an attached image, and repetitively called the inference_most3r function for a series of videos.
Then, this job causes the CUDA OOM error after processing several dozens of images.
I think this code seems pretty similar to pose_eval.py as you mentioned.
How can I fix it?
Thank you for sharing a nice work!
I'm currently using monst3r by repetitively reconstructing 3D point clouds for a series of videos.
However, I observed that there is a GPU memory leakage, where the GPU memory gradually increases and finally the CUDA OOM error occurs after handling several dozens of images.
I've tried to delete the 'scene' variable memory by inserting
del scene
after global_alignment, but it doesn't address the issue.Can you help me to address this GPU memory leakage issue?
Thank you in advance.
The text was updated successfully, but these errors were encountered: