-
Notifications
You must be signed in to change notification settings - Fork 456
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
fix pools termination in BOP dataset generation #1086
Conversation
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Matteo Mastrogiuseppe.
|
Thanks a lot for the bug report and PR! Is it possible for you to sign the CLA? This is necessary, so I can merge this. |
4192b9a
to
e4b2eda
Compare
For contributing to BlenderProc you need to sign our Contributor License Agreement. As an individual please sign CLA_individuals.pdf, as a company please sign CLA_entities.pdf and send it to blenderproc@dlr.de |
Hey @cornerfarmer, which kind of CLA should I sign? For individuals or for companies? My main email is associated with the Italian Institute of Technology, where I'm working rn. Many thanks! |
Hey @matteomastrogiuseppe, I think it makes more sense to use the one for individuals, you can also use your work email/address there. Thanks a lot! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you again for the PR!
fix pools termination in BOP dataset generation
Apparently github got confused in the merging process. So this PR is actually merged not closed, the changes are in the main branch. |
See issue (#1084).
Pools are not explicitely closed, and in my case it leads to a progressive filling up of RAM memory.
Manually calling the terminator shouldn't change anything, while at the same time avoiding potential issues.