-
Notifications
You must be signed in to change notification settings - Fork 324
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
Unexpected UnsupportedOperationException with ForkJoinTask instrumentation #1673
Comments
By doing a quick diff, we can see that the extra attribute in the instrumented version comes from |
Steps to reproduce:
The exception is logged as a warning, thus the test will still pass. |
@felixbarny found what caused the issue within Intelij, there is another agent that modifies the class our agent is also instrumenting (but without the changes from the other agent, hence the conflict). Here is a screenshot where to look for the checkbox to avoid this: Alternatively, if needed to use async stack traces when debugging (which is definitely convenient), you have to temporarily disable instrumentation of |
@SylvainJuge anything we can do in order to close this issue? For example, if it's due to IntelliJ's agent retransform-incapable, is there anything we can do about that? |
An
UnsupportedOperationException
is thrown during ForkJoinTask instrumentation.JVM: OpenJDK 11.0.8 (AdoptOpenJdk).
Found while executing instrumentation unit tests in the IDE.
The class
java.util.concurrent.ForkJoinTask
seems to be redefined at least twice with a different number of attributes, which trigger the exception.By abusing some debugger watches, I managed to capture the following class dumps:
class-dump.zip
It seems that our instrumentation adds a class attribute, whereas we should not modify the class structure.
Full exception stack trace
The text was updated successfully, but these errors were encountered: