On Fri, 24 Mar 2023 07:28:27 GMT, Jaroslav Bachorik <jbacho...@openjdk.org> wrote:
> > Yes, but while JFR interrupts threads too, its sampler runs in its own > > thread, so the async-safety of the interrupted code should not matter, or? > > And this sampling approach is quite subpar when compared with the signal > based profiling - both in terms of bias and precision. Meaning that if/when > JFR would implement a state-of-the-art CPU profiler it will have to deal with > the same issues we are seeing here. Not if they run the walker outside the sampled thread. Which would be much safer in a lot of ways. ------------- PR Comment: https://git.openjdk.org/jdk/pull/13144#issuecomment-1482392946
