Skip to content
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

Twice call to distructor ~NullImplFRVT11() #41

Closed
fisakhan opened this issue Aug 10, 2020 · 1 comment
Closed

Twice call to distructor ~NullImplFRVT11() #41

fisakhan opened this issue Aug 10, 2020 · 1 comment

Comments

@fisakhan
Copy link

The NIST API calls ~NullImplFRVT11() two times after each call to "bin/validate11 createTemplate -x enroll -c $configDir -o $outputDir -h $outputStem -i $inputFile -t $numForks -j $templatesDir retEnroll=$?" Both the destructors use different process ids. This does not allow my program to release memory. I expect only one call to ~NullImplFRVT11(). Whats the problem and how to restrict processes to only one?

@mlngan
Copy link
Collaborator

mlngan commented Aug 18, 2020

The testdriver forks child processes to do work, and the destructor gets called once for each child process + once for the parent process. We use this approach in our actual test, so you will need to address this.

@mlngan mlngan closed this as completed Aug 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants