My Oracle Support Banner

Java SE Frequent Full GCs Occur when JFR Default Recordings Are Requested (Doc ID 2760409.1)

Last updated on MARCH 22, 2021

Applies to:

Java SE JDK and JRE - Version 7 and later
Information in this document applies to any platform.

Symptoms

Full Garbage Collections (GCs) are initiated approximately every minute for reason of "Heap Inspection Initiated GC" when default Java Flight Recorder (JFR) recordings are requested with the following java command line argument:

This began occurring after updating JDK 7 to a recent update.  Only a default recording is enabled, which does not have any special profiling or heap statistics settings that would trigger Full GCs.  The problem does not occur when removing the JFR flag.


Changes

In this one particular case, the 'default.jfr' file was changed shortly after updating to a recent JDK update, so the issue appeared to have something to do with the JDK update itself.  which turned out not to be the case.  The issue occurred only because of the manual changes to the 'default.jfr' file.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.