JDK-8113884 : Memory leak in VirtualFlow when sorting by a column
Type:Bug
Component:javafx
Sub-Component:controls
Affected Version:fx2.0
Priority:P3
Status:Closed
Resolution:Fixed
Submitted:2011-08-09
Updated:2015-06-16
Resolved:2011-08-09
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
Continuously sorting a table by a column makes it perform slower and slower eventually resulting in OOM.
Comments
verified on build 42.
30-08-2011
The issue as described in my first comment is apparently fixed.
The symptoms remain, although to a much lesser degree and due to a different cause, for which a new issue will be filed once validated.
29-08-2011
Please, provide a method on how to check this, or bug will be closed in two weeks. Build 42: (I tried to sort by columns in helloTableView many times and saw, how information in come columns disappear. I'll check this again and it will be a new bug, but i didn't see becoming more slow). If that enough to check performance bug, let me know, or close this bug.
27-08-2011
Another scenario affected by this is rotating rows, essentially doing data.add(data.remove(0)) (PERF-172)
09-08-2011
Thanks - I optimised some code in TableViewSkin such that VirtualFlow.cellCount was only updated if the oldValue != newValue. This inadvertently resulted in the sheet.children list never being cleared. I'll work on a patch that resolves this (by removing my initial optimisation the leak goes away).
09-08-2011
This issue is very similar to RT-13965: sorting adds more and more cells to VirtualFlow.sheet which never gets cleared.