OOM error caused by large array allocation in G1
thomas.schatzl at oracle.com
Tue Nov 21 13:59:43 UTC 2017
On Tue, 2017-11-21 at 21:48 +0800, Lijie Xu wrote:
> Hi Thomas,
> > > I want to know whether my guess is right ...
> > Very likely. This is a long-standing issue (actually I have once
> > investigated about it like 10 years ago on a different regional
> > collector), and given your findings it is very likely you are
> > correct.
> > The issue also has an extra section in the tuning guide.
> ==> This reference is very helpful for me. Another question is that
> "Do Parallel and CMS collectors have this defect too"?
No. Parallel and CMS full GC always move all objects. I filed JDK-81915
65  to at least avoid the OOME. Maybe it can be fixed by jdk 11.
More information about the hotspot-gc-dev