The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
We are trying to reach a safepoint and so the Threads_lock is held by the VMThread. But we have not yet reached the safepoint as some thread(s) is not safepoint-safe. This seems to be the culprit:
Thread 13 (Thread 0x7ffad8287700 (LWP 2737656)):
#0 0x00007ffb088721d0 in nanosleep () from /lib64/libpthread.so.0
#1 0x00007ffb07acc496 in os::naked_short_sleep(long) () from /opt/mach5/mesos/work_dir/jib-master/install/jdk-23+12-837/linux-x64.jdk/jdk-23/lib/server/libjvm.so
#2 0x00007ffb077438ae in JfrRecorderService::emit_leakprofiler_events(long, bool, bool) () from /opt/mach5/mesos/work_dir/jib-master/install/jdk-23+12-837/linux-x64.jdk/jdk-23/lib/server/libjvm.so
#3 0x00007ffb0771e138 in jfr_emit_old_object_samples () from /opt/mach5/mesos/work_dir/jib-master/install/jdk-23+12-837/linux-x64.jdk/jdk-23/lib/server/libjvm.so
#4 0x00007ffaf0188dc9 in ?? ()
#5 0x8000000000000001 in ?? ()
#6 0x0000000000000000 in ?? ()
As there is no naked_short_sleep in emit_leakprofiler_events (which transitions the thread from native to VM, thus making it not-safepoint-safe) we seem to have inlined several functions I suspect we have called LeakProfiler::emit_events and then EventEmitter::emit, but that path beyond that is unclear.
Based on the above I am transferring this to JFR for analysis.