Details
-
Bug
-
Resolution: Fixed
-
P2
-
14
-
b31
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8236881 | 15 | Kim Barrett | P2 | Resolved | Fixed | b06 |
Description
If using jcmd to trigger concurrent cycles (VM is started with -XX:+ExplicitGCInvokesConcurrent) we will hit this assertion if the request is done after the concurrent mark thread is shutdown:
# Internal Error (open/src/hotspot/share/gc/g1/g1CollectedHeap.cpp:2207), pid=25508, tid=25636
# assert(!op.gc_succeeded() || (old_marking_started_before != old_marking_started_after)) failed: invariant: succeeded true, started before 41, started after 41
The reason is that we in do_collection_pause_at_safepoint() realize we are about to shutdown and don't trigger a concurrent cycle, which leads to the counter not being incremented.
VM_G1TryInitiateConcMark should be updated to handle this case.
# Internal Error (open/src/hotspot/share/gc/g1/g1CollectedHeap.cpp:2207), pid=25508, tid=25636
# assert(!op.gc_succeeded() || (old_marking_started_before != old_marking_started_after)) failed: invariant: succeeded true, started before 41, started after 41
The reason is that we in do_collection_pause_at_safepoint() realize we are about to shutdown and don't trigger a concurrent cycle, which leads to the counter not being incremented.
VM_G1TryInitiateConcMark should be updated to handle this case.
Attachments
Issue Links
- backported by
-
JDK-8236881 Assertion when triggering concurrent cycle during shutdown
-
- Resolved
-
- relates to
-
JDK-8236031 Refactor VM_G1TryInitiateConcMark
-
- Open
-