Alexandr,
that sounds right.
It took me a while to figure out the exact circumstances to trigger this
memory leak.
In my application where I found this bug, I have a progress bar which is
repeatedly switched from between visible and invisible, and between
determinate and indeterminate.
I could pr
On 7/19/2016 4:33 PM, Robin Stevens wrote:
Hello Alexandr,
very valid remark.
Running that same test program on Linux with the metal look and feel
reveals no memory leak. I have no access to a Windows machine, so I
couldn't get the Windows specific look and feel.
The other ProgressBarUI impl
Hello Alexandr,
very valid remark.
Running that same test program on Linux with the metal look and feel
reveals no memory leak. I have no access to a Windows machine, so I
couldn't get the Windows specific look and feel.
The other ProgressBarUI implementations seem to extend from
BasicProgressBar
On 7/19/2016 12:27 PM, Robin Stevens wrote:
Hello,
I wanted to discuss my approach for issue JDK-8161664
(https://bugs.openjdk.java.net/browse/JDK-8161664) before I started
working on this issue.
In certain scenarios (see the JIRA issue for an example), the Timer in
the Animator inner class
Hello,
I wanted to discuss my approach for issue JDK-8161664 (
https://bugs.openjdk.java.net/browse/JDK-8161664) before I started working
on this issue.
In certain scenarios (see the JIRA issue for an example), the Timer in the
Animator inner class of the AquaProgressBarUI class remains running,
