Strange behaviour on half-occupied heap

[Simon Ogorodnik]

> On 29 Aug 2018, at 17:46, Aleksey Shipilev <shade at redhat.com> wrote:
> 
> On 08/29/2018 04:44 PM, Simon Ogorodnik wrote:
>> 
>> 
>>> On 29 Aug 2018, at 17:30, Aleksey Shipilev <shade at redhat.com <mailto:shade at redhat.com>> wrote:
>>> 
>>> That are quite probably the used space after previous Full GC. It resets all live data to "Shared"
>>> after collection.
>> 
>> There is only one Full GC since start, and heap already filled with ’Shared allocs’ at its point
> 
> Second guess then: humongous objects are taking the Shared allocation route, and the rest is
> Visualizer troubles.
> 
> Thanks,
> -Aleksey
> 

Might be, but most of this objects is lower then one region

> On 29 Aug 2018, at 17:30, Aleksey Shipilev <shade at redhat.com <mailto:shade at redhat.com>> wrote:

> Thanks! Heap dumps do not yield any suspicion. There are lots of int[] arrays from BufferedImage's,
> which I would expect from IDE workload.

According to YourKit there are actually a lot of int arrays retained by BufferedImage’s, but those BufferedImage’s also unreachable

That’s also true according to VisualVM
Also, almost all of those int arrays goes away after Full GC

Here is a screen-shots of VisualVM & YourKit
https://drive.google.com/file/d/1nkZ2ztqzAP9ZU8kovyDo8zNnFCbMtNwO/view?usp=sharing <https://drive.google.com/file/d/1nkZ2ztqzAP9ZU8kovyDo8zNnFCbMtNwO/view?usp=sharing>