Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 328806 - performance for opening context menu on large tree
Summary: performance for opening context menu on large tree
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows 7
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-27 06:04 EDT by Jörg Bolay CLA
Modified: 2019-08-08 15:32 EDT (History)
4 users (show)

See Also:

Attachments
call tree from a profiler (1.53 MB, text/html)
2010-10-27 06:06 EDT, Jörg Bolay CLA 		no flags Details
hot spots from profiler (55.16 KB, text/html)
2010-10-27 06:07 EDT, Jörg Bolay CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jörg Bolay CLA 2010-10-27 06:04:36 EDT 
Build Identifier: 3.5.2

opening a context menu on a resonable large selection (10000 objects 6 levels deep from root) in a treeviewer takes about 20s. During the time it takes to open the context menu 57 times the Tree.getSelection is called. For every selected item (10000 objects) the path to root is constructed (6 objects). These calls to getSelection take up the lions share of the time till context menu opens. 

Reproducible: Always

Steps to Reproduce:
1. create a tree with a hirachy 6 deep 
2. create a list with 10000 objects in it 
3. select all 10000 objects
4. open a context menu on the selection
Comment 1 Jörg Bolay CLA 2010-10-27 06:06:16 EDT 
Created attachment 181815 [details]
call tree from a profiler
Comment 2 Jörg Bolay CLA 2010-10-27 06:07:06 EDT 
Created attachment 181816 [details]
hot spots from profiler
Comment 3 Eclipse Genie CLA 2019-08-08 11:42:07 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.

--
The automated Eclipse Genie.
Comment 4 Lars Vogel CLA 2019-08-08 15:32:52 EDT 
Nikita, is this bug still relevant? If yes, please remove stalebug flag.