Community
Participate
Working Groups
Build 20020602 (F2) If you start a new workspace, the external tools plugin gets activated on startup. This appears to be related to updating the menu contribution provided by this plugin. Plugins should not be activated just to create a menu item. You can verify this by adding the following to your .options file: org.eclipse.core.runtime/debug=true org.eclipse.core.runtime/timing/startup=true I will attach the stack trace from the activation.
Created attachment 1185 [details] Stack trace of plugin activation
Only occurs with dropdown tool items (class WWinPluginPulldown). Too risky to change at this stage. The Debug items use this too. This could definitely be contributing to our startup time though. E.g. Debug will be activated when in Java perspective.
Reopened for investigation
Notice that the action being contributed is both for the tool bar and menu bar. When the tool bar is being populated, the pull down menu of the tool item representing the action is not created at that time and therefore the delegate is not created nor is the plugin loaded. But because its also an action for the menu bar and states it's a cascading menu item, the menu bar update code forces the delegate to load so the menu is properly updated. Until we address the issue of dynamic menu contributions, I suggest we hold off doing anything on this at the moment. Therefore, downgrading the priority.
See also bug 27460
Why does the menubar code ask for the children before the menu is shown?
There were lots of reasons. For example, keeping the accelerators up-to-date. The problem only started showing up a few months ago it seems because of some changes done to support the cheveron menu. Nevertheless, we may have a potential workaround and we are looking at true support for dynamic menus (the ones giving us this problem at the moment)
Moving to Eduardo for the fix to lazily populate menus. Filed bug 27867 for future work to improve the management of dynamic items.
*** Bug 27360 has been marked as a duplicate of this bug. ***
We can't lazy populate the menu in this case. We need a real solution for this problem with new API.
*** Bug 28074 has been marked as a duplicate of this bug. ***
To investigate and come up with a "light-weight" proposal for 2.1 which will allow us to extend in a future release.
This obviously did not make it into 2.1. This will be considered under Bug 36968 for 3.0, but might not make it into the final release.
Deferring until after M9.
Marking as LATER
*** Bug 27460 has been marked as a duplicate of this bug. ***
Reopening to mark as dup.
*** This bug has been marked as a duplicate of bug 53979 ***
