| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8082886 | emb-9 | Mikael Gerdin | P3 | Resolved | Fixed | team |
The change is incomplete since several places in the GC code assumes that explicit gcs have the _java_lang_system_gc GCCause value in order to determine the behavior.
For example:
ParallelGC does not apply policy decisions on user-invoked GCs (decided by the GCCause)
G1/CMS honors +ExplicitGCInvokesConcurrent based on the GCCause setting.
This could cause problems for people expecting concurrent gcs when running the diagnostic command instead of a possibly several-second full gc pause.
For example:
ParallelGC does not apply policy decisions on user-invoked GCs (decided by the GCCause)
G1/CMS honors +ExplicitGCInvokesConcurrent based on the GCCause setting.
This could cause problems for people expecting concurrent gcs when running the diagnostic command instead of a possibly several-second full gc pause.
- backported by
-
JDK-8082886 [BACKOUT] GCCause should distinguish jcmd GC.run from System.gc()
-
- Resolved
-
- relates to
-
JDK-8072743 jcmd output change breaks tests
-
- Closed
-
-
-
- Closed
-
-
JDK-8072913 [REDO] GCCause should distinguish jcmd GC.run from System.gc()
-
- Resolved
-
-
-
- Closed
-