-
Enhancement
-
Resolution: Fixed
-
P3
-
hs24
-
b09
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2224285 | 8 | Bengt Rutisson | P3 | Closed | Fixed | b38 |
JDK-8018203 | 7u45 | Bengt Rutisson | P3 | Closed | Fixed | b01 |
JDK-8002479 | 7u40 | Bengt Rutisson | P3 | Closed | Fixed | b01 |
It would be much simpler to figure out why a GC happens if the GC cause was part of the information logged for each GC.
Just recently we were debugging a case where G1 was doing a lot of full GCs when running Eclipse. It turned out that the GCs where caused by perm gen running out of memory. This would have been much faster to find out if this was part of the logging.
Just recently we were debugging a case where G1 was doing a lot of full GCs when running Eclipse. It turned out that the GCs where caused by perm gen running out of memory. This would have been much faster to find out if this was part of the logging.
- backported by
-
JDK-2224285 G1: Log GC Cause for a GC
-
- Closed
-
-
JDK-8002479 G1: Log GC Cause for a GC
-
- Closed
-
-
JDK-8018203 G1: Log GC Cause for a GC
-
- Closed
-
- relates to
-
JDK-7166894 Add gc cause to GC logging for all collectors
-
- Closed
-