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
OOM when running with valgrind #101
Comments
This is the command I am running |
Running within an Ubuntu 16.04 docker container. |
Just to know, are you using the cuda version or the cpu version? Do you have the same if u run it with |
I am using the stand alone version (i.e the non cuda version) I didn't build a library with the CUDA version. I can give it a shot next. |
I was asking because in the cuda version there are a lot of dynamic allocations but it should not be the case in the cpu. |
Hi I got on a server that has 128GB of memory and ran the test. I see the total memory consumption goes upto 25GB (that explains why it didn't run on my laptop) Find the valgrind output attached |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I tried to run valgrind on the detection algorithm. I see memory consumption go up continously. It reaches 15GB and kills my wks. Have any of you encountered similar issues
The text was updated successfully, but these errors were encountered: