-
Notifications
You must be signed in to change notification settings - Fork 66
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
gpu memory not realesed #56
Comments
Hi, there might be a memory leak. I'll try to find a time to investigate further after a deadline recently. |
Hi, @wenbowen123. Thank you for the swift reply. I am doing test on both online and offline data. The suggestion is a great solution for offline data, thanks. However, for oneline test, it does not work. |
I also have this problem right now. I tried the workaround to split my dataset into smaller segments, but it would be great if there's a solid solution. |
FYI, we recently released a follow up version BundleSDF, which should not have such issue. |
Hi @wenbowen123,
thank you for your nice work. I've been trying to run Bundletrack on a collections of video clips.
To automatically swith between each clips, I simply declare Bundler by
*Bundler bundler = nullptr; before the main loop of video
and construct it again after swith to to a new video clips by
delete bundler;
bundler = new Bundler(yml,&data_loader); . The pose estimation result seem well. However, I find that the GPU memory is not realesed after swith to a new video clips and the usage keeps increaseting. Untill 10G GPU memory was used, the programe will be automatically killed by no reason.
Do you have any idea of how to resolve this issue?
The text was updated successfully, but these errors were encountered: