RFR: 8357915: SecureRandom nextLong memory usage

[Sean Mullan]

On Thu, 26 Jun 2025 18:00:21 GMT, Koushik Muthukrishnan Thirupattur <duke at 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.

A CSR should be filed, since you are overriding a public method.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/26005#issuecomment-3019048117