-
Bug
-
Resolution: Fixed
-
P3
-
8u40
-
Windows 7 64-bit
Java 8u40
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8129482 | 8u60 | Jonathan Giles | P3 | Resolved | Fixed |
Tracking down a leak in my application I found that tens of thousands of BindingHelperObserver and WeakReference objcts were accumulating, all rooted in an indeterminate ProgressBar that wasn't even visible.
Using jvisualvm to compare heap dumps at various points (after forcing GC), I see the following chain of objects:
WeakReference
BindingHelperObserver
InvalidationListener[]
ExpressionHelper$Generic
Node$NodeTransformation$2
Node$NodeTransformation
StackPane
ProgressBarSkin
ProgressBar
or
WeakReference
BindingHelperObserver
InvalidationListener[]
ExpressionHelper$Generic
ProgressBarSkin$1
ProgressBarSkin
ProgressBar
(The one with the NodeTransformation appears to be related to the animated style of the indeterminate ProgressBar.)
After changing my application to force the invisible progress bar to have a progress value of 0.0 (it was initially left at the default of -1.0), I could no longer reproduce the leak.
Using jvisualvm to compare heap dumps at various points (after forcing GC), I see the following chain of objects:
WeakReference
BindingHelperObserver
InvalidationListener[]
ExpressionHelper$Generic
Node$NodeTransformation$2
Node$NodeTransformation
StackPane
ProgressBarSkin
ProgressBar
or
WeakReference
BindingHelperObserver
InvalidationListener[]
ExpressionHelper$Generic
ProgressBarSkin$1
ProgressBarSkin
ProgressBar
(The one with the NodeTransformation appears to be related to the animated style of the indeterminate ProgressBar.)
After changing my application to force the invisible progress bar to have a progress value of 0.0 (it was initially left at the default of -1.0), I could no longer reproduce the leak.
- backported by
-
JDK-8129482 Invisible Indeterminate ProgressBar has memory leak
-
- Resolved
-
- relates to
-
JDK-8096912 [TabPane] TableView in TabPane has memory leak
-
- Resolved
-