-
Bug
-
Resolution: Fixed
-
P3
-
8
-
8.0-graphics-scrum-b1845-x64, Windows 7 x64
Steps to reproduce:
- Run Ensemble8 in Monitor Application profile mode
- Repeat the following steps several times:
- Navigate to Menu sample
- Click menu to see menu popup
- Navigate back to home page
- Dump heap
- Use the following OQL query to see what SamplePage instances were not garbage collected:
select { SamplePage: x, title: x.titleProperty.value.toString() }
from ensemble.samplepage.SamplePage x
- There would be a SamplePage instance for each repetition of the steps above
- Check out nearest GC roots for each SampePage instance.
- Most of them would contain the following pattern:
ContextMenu -> ownerNode -> ... -> MenuBar
- One more would have accelerator pattern (covered byRT-33691)
Samples that have no ContextMenu invocations would be garbage collected. SeeRT-33691 for the reproducible case.
- Run Ensemble8 in Monitor Application profile mode
- Repeat the following steps several times:
- Navigate to Menu sample
- Click menu to see menu popup
- Navigate back to home page
- Dump heap
- Use the following OQL query to see what SamplePage instances were not garbage collected:
select { SamplePage: x, title: x.titleProperty.value.toString() }
from ensemble.samplepage.SamplePage x
- There would be a SamplePage instance for each repetition of the steps above
- Check out nearest GC roots for each SampePage instance.
- Most of them would contain the following pattern:
ContextMenu -> ownerNode -> ... -> MenuBar
- One more would have accelerator pattern (covered by
Samples that have no ContextMenu invocations would be garbage collected. See
- blocks
-
JDK-8123957 Ensemble8: running out of memory
-
- Resolved
-
- relates to
-
JDK-8120252 Controls are leaking through focus owner mechanism
-
- Resolved
-
-
JDK-8116412 Controls are leaking through mnemonics and accelerators
-
- Closed
-