Bug 221708 - Pressing '*' on "Plug-In Dependencies"-View causes Eclipse to populate the tree endless.
Summary: Pressing '*' on "Plug-In Dependencies"-View causes Eclipse to populate the tr...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3.1   Edit
Hardware: PC All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: bugday
Depends on:
Blocks:
 
Reported: 2008-03-06 14:02 EST by Marco Maniscalco CLA
Modified: 2019-09-09 02:24 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Maniscalco CLA 2008-03-06 14:02:44 EST
Pressing '*' on "Plug-In Dependencies"-View causes Eclipse to populate the tree endless.
Comment 1 Chris Aniszczyk CLA 2008-03-06 14:28:12 EST
I don't see this problem in the latest build of Eclipse...

Can you provide a stacktrace or some other information?
Comment 2 Benjamin Cabé CLA 2008-03-08 17:41:58 EST
I can't reproduce it either on 3.3.1.1 :/
We need more info, Marco :)
Comment 3 Marco Maniscalco CLA 2008-03-08 18:06:03 EST
Ok I have WinXP and fresh Eclipse Version: 3.3.1 Build id: M20070921-1145.

Pressing * on a regular tree control in Windows environment causes the tree to recursively expand all levels until all leaf nodes are visible. This works e.g. in Explorer treeview.

Maybe this is only a question of memory. I have a RCP project with 10 plugins, referencing many Platform plugins. I tried it, and after blocking a few minutes I see a tree with thousands of nodes :-P (VM ~ 150MB) So I guess this was no bug, only a freaking big structure. Maybe its no good idea to expand the whole tree.
Comment 4 Chris Aniszczyk CLA 2008-04-15 11:52:01 EDT
I still haven't been able to reproduce... maybe I have a fast machine :)

I don't think expanding the whole tree is a good idea... but we should still not crash.

Maybe we can ignore just the "*" case
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:11:51 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 6 Julian Honnen CLA 2019-09-09 02:24:00 EDT
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.