> 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. > So added an implementation in SecureRandom that call nextBytes(8 bytes) and > then convert that to a long.
Koushik Muthukrishnan Thirupattur has updated the pull request incrementally with one additional commit since the last revision: 8357915: SecureRandom nextLong memory usage ------------- Changes: - all: https://git.openjdk.org/jdk/pull/26005/files - new: https://git.openjdk.org/jdk/pull/26005/files/23228fd8..04f859bd Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=26005&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=26005&range=00-01 Stats: 3 lines in 1 file changed: 3 ins; 0 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/26005.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/26005/head:pull/26005 PR: https://git.openjdk.org/jdk/pull/26005
