Hi,
I agree the problem with de-allocation of native memory blocks should be
studied deeply and this takes time.
What I have observed so far on Linux platform (other platforms may
behave differently) is the following:
Deallocation of native memory with Unsafe.freeMemory(address) can take
On 05.10.2013 21:57, Brian Goetz wrote:
Is there something I missed? Is this something that has been considered?
If memory efficiency were the only metric in the world, this would be a
no-brainer. But, by having different classes for different nodes, many many
paths where the VM could
On 10/06/2013 08:09 PM, Philippe Marschall wrote:
On 05.10.2013 21:57, Brian Goetz wrote:
Is there something I missed? Is this something that has been
considered?
If memory efficiency were the only metric in the world, this would be
a no-brainer. But, by having different classes for
As a follow-up to Joe Darcy's rename of jdk.Supported to jdk.Exported,
I'd like to have another attempt at adding the annotation to a number of
JDK specific APIs that are long standing exported, documented and
supported APIs. Specifically, the following APIs:
- Java Debug Interface
Hi Again,
The result of my experimentation is as follows:
Letting ReferenceHandler thread alone to en-queue References and execute
Cleaners is not enough to prevent OOMEs when allocation is performed in
large number of threads even if I let Cleaners do only synchronous
announcing of what
