-
Bug
-
Resolution: Fixed
-
P4
-
jfx20
-
b17
-
generic
-
generic
Some of the system tests check the memory leak using a loop and multiple calls to System.gc() method. These tests can be made more robust by using JMemoryBuddy utility.
E.g.
TabPaneHeaderLeakTest
AccordionTitlePaneLeakTest
ShapeViewOrderLeakTest
SwingNodeMemoryLeakTest
SwingNodeDnDMemoryLeakTest
For reference - systems test that already use JMemoryBuddy utility:
-----------------------------------------------------------------------------------------
ViewPainterLeakTest
PlatformStartupMemoryLeakTest
VirtualFlowMemoryLeakTest
StyleMemoryLeakTest
InitialNodesMemoryLeakTest
ProgressIndicatorLeakTest
E.g.
TabPaneHeaderLeakTest
AccordionTitlePaneLeakTest
ShapeViewOrderLeakTest
SwingNodeMemoryLeakTest
SwingNodeDnDMemoryLeakTest
For reference - systems test that already use JMemoryBuddy utility:
-----------------------------------------------------------------------------------------
ViewPainterLeakTest
PlatformStartupMemoryLeakTest
VirtualFlowMemoryLeakTest
StyleMemoryLeakTest
InitialNodesMemoryLeakTest
ProgressIndicatorLeakTest
- duplicates
-
JDK-8196614 Intermittent failure in test.javafx.embed.swing.SwingNodeMemoryLeakTest
- Closed
- is blocked by
-
JDK-8206430 Use consistent pattern for startup in FX system tests
- Resolved