Replies: 1 comment
-
Some screenshot about my configuration. Hope this helps. Thanks |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
Hope I'm in right place.
I have a problem with NB 21 (but tested with NB 20 too) and instrumented profiler.
Some technical specs:
openjdk version "17.0.9" 2023-10-17
OpenJDK Runtime Environment (Red_Hat-17.0.9.0.9-4) (build 17.0.9+9)
OpenJDK 64-Bit Server VM (Red_Hat-17.0.9.0.9-4) (build 17.0.9+9, mixed mode, sharing)
(rpm Fedora 39 mainline build)
java-atk-wrapper-0.38.0-6.fc34.x86_64
javapackages-filesystem-6.1.0-10.fc39.noarch
tzdata-java-2024a-2.fc39.noarch
java-17-openjdk-headless-17.0.9.0.9-3.fc39.x86_64
javapackages-tools-6.1.0-10.fc39.noarch
java-diff-utils-4.12-3.fc39.noarch
java-17-openjdk-17.0.9.0.9-3.fc39.x86_64
java-17-openjdk-devel-17.0.9.0.9-3.fc39.x86_64
java-17-openjdk-src-17.0.9.0.9-3.fc39.x86_64
To replicate the problem you can create a simple Anagram Game (Ant) or a Java Application (Gradle & Maven).
So, after that you can try to profile the project.
Profile type: Methods
Settings of profile methods: Focused (Instrumented) > Selected classes
And select main class.
Then launch profiler. The result is that the target class never appears in collected data. No threads available in thread selection....none to view.
Same if you try to profile "Selected methods" or "Defined classes"....simply does nothing.
But if you run a General (Sampled) profiler over "all classes" or "project classes" everything works fine.
Has anyone already had this problem? If so how did you solve it?
Many thanks,
Agharta
Beta Was this translation helpful? Give feedback.
All reactions