-
Notifications
You must be signed in to change notification settings - Fork 52
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
potential resource leak #198
Comments
Yes, we have this for a while I think. Some tests just never seem to work when running them locally (i.e. running them for a second time on a machine). So my guess is that it is some kind if permanent handle that does not get removed. I have not been looking closely at this though so I am just guessing. It would be really nice if it could be fixed though. The first thing I would do here in this test would be to remove the |
I triggered the issue elsewhere. A |
I have previously seen this, thought it was solved 😕 damn... We are leaking sessions somewhere, will try and rat it out at some point. |
Ok, turns out something like this happens in the Parsec service sometimes, but it's due to how the service handles signals. @baloo - did the |
no, but after a flush context I could re-run the tests again. |
Hi, just checking if this issue is already being fixed or not as I'm getting a similar error with the unit tests.
|
Hey - is that one of our unit tests? If not, could you post a link to/copy of the test? |
Hi @ionut-arm, It's one of the tests I wrote. It actually tries to make the context static for further use. You can find the minimal function and test on playground The test executes successfully for 3 times and then fails for the remaining time. Any help is appreciated. |
This could be because you are storing Instead of storing |
What version of the rust-tss-esapi is this? If possible could you run it with latest from master and see what the error says? But I think I should point out that I have also seen problems with |
When running tests with swtpm (0.5.2) linked with libtpms(0.8.0). I'm seeing a lot of:
Should I restart the TPM, the tests go further, but still crash at some point.
This is how I start my swtpm:
https://github.com/baloo/reproducibility-lab/blob/baloo/wip/pcr-eventlog-attestation/pkgs/pcr-eventlog-attestation/shell.nix#L152
This would look like a resources leak of some sort.
The text was updated successfully, but these errors were encountered: