-
Notifications
You must be signed in to change notification settings - Fork 583
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
warning "Re-registering of platform native method: jdk.internal.misc.Unsafe.park(ZJ)V from code in a different classloader" #3054
Comments
I was able to get the same issue. All of my logs are filling with this error :/ |
Does the error happen with the async-profiler https://github.com/async-profiler/async-profiler ? Please specify exact java versions (including vendor, build number) or base docker image |
Hi @korniltsev, in my case, it is using Java 21 with the base docker image I don't remember ever seeing this error when using async-profiler, but it's hard to know as I mostly used it on my local machine (no docker). I will try to find some time to test it out, but I have to admit I can't guarantee I will be able to do it soon :P |
Hi @korniltsev, today I tested running some java in the exact same setup as when using pyroscope but without pyroscope and only async-profiler v3.0 added as an agent to the VM arguments and there are no warnings. Since pyroscope loads the agent at runtime, maybe this is where the difference is… also I'm not sure if pyroscope uses the latest version of async-profiler (3.0)? this could also be an explanation… |
we are experiencing the same issue with |
facing the same behaviour even with 0.13.1 javaagent and following env variables:
If I remove |
updates:
so we have multiple times when profiler do class/traps registration and it's create a lot of WARN messages from jvm I also don't know is it correct logic or not to register/de-register async-profiler multiple times |
absolutely, pyroscope should not load asprof twice. I will take a look, this should not be the case. |
Describe the bug
When Pyroscope agent is loaded at runtime on a Java 21 VM, I can see the following warnings every few seconds in the logs:
To Reproduce
The agent is loaded with:
Expected behavior
No warnings
Environment
Additional Context
I found this old JDK bug meant to be fixed in Java 15: https://bugs.openjdk.org/browse/JDK-8239593
The text was updated successfully, but these errors were encountered: