Community
Participate
Working Groups
Build Identifier: I20100608-0911 If you set the current count to 100000, it takes 0 ms but when you set it to 10000 just after, it takes 8656 ms on my computer. The reason is that AbstractTableViewer call doGetItem(i) 90000 times in my example. Reproducible: Always Steps to Reproduce: See attached sample.
Created attachment 175200 [details] sample showing the problem
The problem is with the doGetItem(i) call required for disassociating the items. That call will actually cause the virtual tree to materialize the item at that index. So the attempt to dispose excess items will actually cause their creation. Currently SWT does not provide any API to check if a item at a particular index has been materialized or not. We may be already maintaining information of their state. With some changes this should be possible to fix.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
