Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 319981

Summary:	Virtual TreeViewer.remove(Object) is awful slow
Product:	[Eclipse Project] Platform	Reporter:	Andreas Nusser <a.nusser>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.5.2
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Andreas Nusser

2010-07-15 09:11:16 EDT

Build Identifier: 20100218-1602

Hi,

I've created a virtual TreeViewer where one node has several hundred children. When I call TreeViewer.remove(object) with one of the first children, it takes a couple of seconds until eclipse unfreezes. For comparison: calling TreeViewer.refresh() is almost done immediately. Even more interesting is, that the farther down I try to remove a child, the faster TreeViewer.remove(object) gets.

Reproducible: Always

Steps to Reproduce:
1. Create a virtual treeviewer with several hundred children
2. Remove one of the top children
3. Wait

Comment 1 Eclipse Webmaster

2019-09-06 16:08:06 EDT

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.

Comment 2 Eclipse Genie

2021-09-23 19:58:53 EDT

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.