Uncollected garbage

[Roman Kennke]

> The heap usage is nearly 100% , with these int[] objects occupying 87%. The
> JVM process consumes ~100% of CPU, most of which is GC trying to free up
> some memory. Does this fit into "filler objects" explanation?

Hmm, no, not really.

AFAIK, those image objects carry their int[] for image data, and they 
are accessed by native code, too. Native access to arrays pins the 
arrays and their containing region. It seems plausible that frequent 
native access to image data prevents those regions from being collected, 
at least as long as the region contains one live/reachable image data 
array. Eventually, those *should* be reclaimed.

Can you post heap configuration that is printed by -verbose:gc when 
application starts, and also typical size of the int arrays?

Thanks,
Roman