RFR: JDK-8269092: Add OldObjectSampleEvent.allocationSize field

[Erik Gahlin]

On Wed, 23 Jun 2021 07:39:44 GMT, Ludovic Henry <luhenry at openjdk.org> wrote:

> In the case of memory leak analysis, we then know which objects appear to be leaking. We also know that, based on the heuristics of the priority queue in the leak profiler, the sampled objects have the most impact on memory usage (since sampling is biased towards bigger shallow objects).

Not sure I understand, but it may not matter

> However, we still don't know exactly how much memory is used. We can approximate it if it's an array, based on the size of the elements and the number of elements. However, it's always going to be approximative since the size of the object header might change in the future (project Lilliput), and because of various other constraints like alignement of elements, size of each element, etc.

But why do you need it? 

Is a large (or small?) "allocation size" more likely a leak, or what is the thinking?

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

PR: https://git.openjdk.java.net/jdk/pull/4549