31623 – [performance] Dialogs loaded too soon

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

Bug 31623 - [performance] Dialogs loaded too soon

Summary: [performance] Dialogs loaded too soon

Status:	RESOLVED DUPLICATE of bug 53979

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Debug (show other bugs)
Version:	2.1
Hardware:	PC Windows 2000

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Platform-Debug-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:	performance

Depends on:
Blocks:

Reported:	2003-02-11 22:02 EST by Jeff McAffer
Modified:	2007-06-18 11:11 EDT (History)
CC List:	0 users

See Also:

Attachments
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 Jeff McAffer

2003-02-11 22:02:40 EST

In M5...

Open Eclipse with a perspective which has hidden editors (e.g., the Runtime Spy 
perspective in the Core Tools plugin).  Ensure you have a Java Browsing 
perspective and one open java file available but not visible.  Using the Core 
tools Runtime Spy you can see that there are some 21 classes loaded in the 
Debug UI plugin (the actual number may vary by VM due to verification 
differences).

Now switch to the Java Browsing perspective and then back to the Runtime Spy 
perspective.  Notice that there are now 41 classes loaded in the Debug UI 
plugin.  Below is the list of additional classes in order of loading.  As you 
can see, there are many actions and dialog classes loaded.  Some of this is 
likely due to the UI plugin not being able to defer creating the run/debug menu 
entries.  It does seem however that more than that is being loaded.

org.eclipse.debug.internal.ui.actions.OpenRunConfigurations
org.eclipse.debug.internal.ui.actions.RunAsAction
org.eclipse.debug.internal.ui.actions.RunHistoryMenuAction
org.eclipse.debug.internal.ui.actions.RelaunchLastAction
org.eclipse.debug.internal.ui.actions.DebugLastAction
org.eclipse.debug.internal.ui.actions.RunLastAction
org.eclipse.debug.internal.ui.actions.RunToolbarAction
org.eclipse.debug.internal.ui.actions.OpenDebugConfigurations
org.eclipse.debug.internal.ui.actions.DebugAsAction
org.eclipse.debug.internal.ui.actions.DebugHistoryMenuAction
org.eclipse.debug.internal.ui.actions.DebugToolbarAction
org.eclipse.debug.ui.actions.LaunchAction
org.eclipse.debug.ui.DebugUITools
org.eclipse.debug.ui.ILaunchConfigurationDialog
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationProperties
Dialog
org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog
org.eclipse.debug.internal.ui.DefaultLabelProvider
org.eclipse.debug.internal.ui.DebugPluginImages
org.eclipse.debug.internal.ui.IDebugHelpContextIds

Comment 1 Darin Wright

2003-02-12 12:06:30 EST

The actions refer to the dialogs (they can open the dialogs). The label 
provider is used to create images for the actions. The help context ids are 
used in the actions as well.

I do not see much opportunity here - unless we use ugly "classForName" tricks.

Comment 2 Darin Wright

2003-02-13 21:09:14 EST

Nothing planned for 2.1

Comment 3 Darin Wright

2007-06-18 11:11:17 EDT

Closing, this is really a dup of bug 53979, and we also have bug 191723 to improve our class loading on startup.

Comment 4 Darin Wright

2007-06-18 11:11:44 EDT


*** This bug has been marked as a duplicate of bug 53979 ***