On Mon, 30 Jun 2025 17:45:23 GMT, Koushik Muthukrishnan Thirupattur <d...@openjdk.org> wrote:
>> 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 @koushikthirupattur Your change (at version 04f859bdec18f767bf33156939a02f4a336c42e2) is now ready to be sponsored by a Committer. ------------- PR Comment: https://git.openjdk.org/jdk/pull/26005#issuecomment-3049806984
