The continuations preempt_epilog() makes a call to the overloaded version of freeze_epilog(ContinuationWrapper& cont) which does not have the call:
JVMTI_ONLY(jvmti_yield_cleanup(thread, cont)); // can safepoint
The function is below:
static inline freeze_result freeze_epilog(ContinuationWrapper& cont) {
verify_continuation(cont.continuation());
assert(!cont.is_empty(), "");
log_develop_debug(continuations)("=== End of freeze cont ### #" INTPTR_FORMAT, cont.hash());
return freeze_ok;
}
JVMTI_ONLY(jvmti_yield_cleanup(thread, cont)); // can safepoint
The function is below:
static inline freeze_result freeze_epilog(ContinuationWrapper& cont) {
verify_continuation(cont.continuation());
assert(!cont.is_empty(), "");
log_develop_debug(continuations)("=== End of freeze cont ### #" INTPTR_FORMAT, cont.hash());
return freeze_ok;
}
- relates to
-
JDK-8368159 Significant performance overhead when started with jdwp agent and unattached debugger
-
- Resolved
-
-
JDK-8369482 JVMTI + Loom: JDK-8368159 introduced safepoint poll in disallowed state
-
- New
-