JDK-8251286 : [macos] CPU usage issue on Aqua L&F JProgressBar
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 11,14,15,16
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: os_x
  • Submitted: 2020-08-07
  • Updated: 2020-08-08
  • Resolved: 2020-08-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdResolved
Related Reports
Duplicate :  
Description
Even if Progress Bar was stopped (suspended), CPU resource was exhausted.
I could see this issue with High Sierra, Mojave, Catalina.

Test instruction is as follows:
1. Start "Activity Monitor" via Finder
2. On "Window" menu, select "CPU History"
3. Start java with SwingSet2 demo
4. Please wait until CPU usage is stable
5. Click JProgressBar Demo icon on JToolBar (9th icon from left side)
6. Press "Start Loading Text" button, and wait a few seconds
7. Press "Stop Loading Text" button
8. By step 6, CPU usage becomes HIGH, by step 7, CPU usage should be becomes LOW
9. On "Look & Feel" menu on SwingSet2, select "Java Look & feel", CPU usage becomes LOW
10. On "Look & Feel" menu on SwingSet2, select "Mac OS X Look & feel", CPU usage becomes higher

Same kind issue was reported by JDK-8147843, but I think usage was not same.
 

Comments
For Java L&F, the CPU usage varies between 10-20% from start to finish of JProgressBar demo For Aqua L&F, the CPU usage varies between 14-55% from start to finish. I made sure SwingSet2 CPU usage falls back to 0.1% before commencing the test. It seems while the crash is solved by JDK-8146238, the high CPU usage is not solved.
08-08-2020