You get JFR's precision but inherit its blind spots as described in [1]: *> demo...

		omazurov on March 29, 2023 \| parent \| context \| favorite \| on: Writing a Profiler in 240 lines of pure Java You get JFR's precision but inherit its blind spots as described in [1]: > demo1: ... JFR will not report anything useful at all, since it cannot traverse stack traces when JVM is running System.arraycopy() I'd rather run jstack in a loop than lose System.arraycopy() (or, in fact, any native code be it JVM's or JNI). [1] https://github.com/apangin/java-profiling-presentation

I would rather use Andrei Pangin's async-profiler than doing something custom with jstack.