-
Notifications
You must be signed in to change notification settings - Fork 325
Closed
Labels
Description
Describe the bug
After profiling finished for a terminated application, starting the same application again and profiling it causes the Profiler tab of the original application to update as well.
To Reproduce
- Create a small Java program, for example
class Test { public static void main(String... args) throws Exception { System.out.println("Press ENTER to exit"); System.in.read(); } }
- Run the program with
java Test.java
(requires Java 11 or newer) - In VisualVM start CPU profiling the application with "Profile classes: **"
- In the console from step 2 press ENTER to terminate the application
- In VisualVM select "No" to not create a profiling results snapshot
- Repeat steps 2 and 3
- In VisualVM look at Profiler the tab of the terminated application
❌ Bug: It updates based on the currently running application, even though that is a separate application
Expected behavior
The Profiler tab should not update for terminated applications.
VisualVM log
logfile.txt
The video shows the steps described in the "To Reproduce" section above:
- Profiling is started
- Application is stopped
- Application is started again (separate PID)
- Profiling is started
❌ Bug: Profiler tab of terminated application is updated by VisualVM
Desktop (please complete the following information):
- OS: Windows 10
- JDK version JDK 11.0.13+8
- Version 2.1.4