-
Bug
-
Resolution: Fixed
-
P3
-
8u20
It's possible for ProgressIndicators/Bars to "leak" Animations and thus keep the scene pulsing and cpu burning. I wasn't able to figure out why this happens by reading the code, as the right codepaths do seem to be present, but nonetheless if I do setVisible(false) on a parent of an indeterminate ProgressIndicator, or remove the parent of an indeterminate ProgressBar from the scene graph, I can clearly see the animations are still registered in Toolkit.getToolkit().getMasterTimer().receivers and cpu usage remains high.
My hack around this issue is to set the progress bar/indicator to some definite percentage before it has a chance to be set invisible or removed from the scene graph. This forces it to stop the animation. If I don't do this, the animation stays alive somehow.
My hack around this issue is to set the progress bar/indicator to some definite percentage before it has a chance to be set invisible or removed from the scene graph. This forces it to stop the animation. If I don't do this, the animation stays alive somehow.
- relates to
-
JDK-8094829 Memory leak in JavaFX ProgressIndicator
- Resolved
-
JDK-8151165 ProgressIndicator indeterminate transition initializated even in non visible controls
- Resolved
-
JDK-8151166 Progress Indicator indeterminate transition not stopped when component is not visible
- Resolved
-
JDK-8148827 Indeterminate ProgressBar initially tree invisible does not animate until layoutChildren()
- Resolved