Memory leak in Prf #53
Description
Help us help you
We'd like to know more about
your Tink deployment.
Describe the bug:
Memory leak in Tink Prf Java See here for detailed description: #52
What was the expected behavior?
Not to drain memory in repetitive calls to prf.compute().
How can we reproduce the bug?
See here for reproducing steps: #52
Do you have any debugging information?
Using memory profiler this is the leak stacktrace:
java.lang.Thread.State: RUNNABLE
at jdk.internal.misc.Unsafe.allocateMemory0(java.base@17.0.14/Native Method)
at jdk.internal.misc.Unsafe.allocateMemory(java.base@17.0.14/Unsafe.java:630)
at java.nio.DirectByteBuffer.<init>(java.base@17.0.14/DirectByteBuffer.java:125)
at java.nio.ByteBuffer.allocateDirect(java.base@17.0.14/ByteBuffer.java:332)
at com.google.crypto.tink.subtle.prf.HkdfStreamingPrf$HkdfInputStream.initialize(HkdfStreamingPrf.java:88)
at com.google.crypto.tink.subtle.prf.HkdfStreamingPrf$HkdfInputStream.read(HkdfStreamingPrf.java:129)
at com.google.crypto.tink.subtle.prf.PrfImpl.readBytesFromStream(PrfImpl.java:45)
at com.google.crypto.tink.subtle.prf.PrfImpl.compute(PrfImpl.java:67)
at com.google.crypto.tink.prf.PrfSet.computePrimary(PrfSet.java:44)
See here for
What version of Tink are you using?
For example, 1.7.0. but it's present on master too.
Can you tell us more about your development environment?
Such as JDK 8
Is there anything else you'd like to add?
Metadata
Metadata
Assignees
Labels
No labels