-
CSR
-
Resolution: Unresolved
-
P4
-
None
-
minimal
-
Java API
-
SE
Summary
SecureRandom nextLong memory usage enhancement
Problem
SecureRandom uses straightforward implementations inherited from Random but in the process does double the memory allocations necessary.
The delegation to SecureRandom.engineNextBytes does not provide int
or long
values, the caller must allocate a byte array and assemble the value itself.
Solution
Add an implementation in SecureRandom that call nextBytes(8 bytes) and then convert that to a long
Specification
See attached
- csr of
-
JDK-8357915 SecureRandom nextLong memory usage
-
- In Progress
-