-
Sub-task
-
Resolution: Duplicate
-
P3
-
None
-
8
-
8.0-graphics-scrum-b1845-x64, Windows 7 x64
Steps to reproduce:
- Run Ensemble in Monitor Application profile mode
- Go to MenuBar sample
- Go to some other sample
- Create a memory dump
- Use the following OQL query to see that Menu sample page is not garbage collected:
select { SamplePage: x, title: x.titleProperty.value.toString() }
from ensemble.samplepage.SamplePage x
- See the nearest GC root of "Menu" sample SamplePage instance
- Notice keyboardShortcutsHandler > accelerators > ... value, where value key KeyCodeCombination which code is F10.
- Run Ensemble in Monitor Application profile mode
- Go to MenuBar sample
- Go to some other sample
- Create a memory dump
- Use the following OQL query to see that Menu sample page is not garbage collected:
select { SamplePage: x, title: x.titleProperty.value.toString() }
from ensemble.samplepage.SamplePage x
- See the nearest GC root of "Menu" sample SamplePage instance
- Notice keyboardShortcutsHandler > accelerators > ... value, where value key KeyCodeCombination which code is F10.
- blocks
-
JDK-8123957 Ensemble8: running out of memory
- Resolved
- duplicates
-
JDK-8117406 MenuBar sample seems to be leaking through F10 accelerator
- Resolved