Community
Participate
Working Groups
using RAD v7.0.0.3 which uses org.eclipse.jdt.debug.ui_3.2.2.r322_v20061205.jar scenario is as follows: - start RAD against a 110+ projects (various natures - Java, J2EE, Data, Web) - wait until no background job is running - open the Debug - Create, Manage, and Run configurations. - in the left-hand tree, right-click Eclipse Application and select new --> I have to wait between 90 and 120 sec before the new config page is displayed, which is strange and annoying from a user perspective. Note that in RAD, we have many possible launch config (see to_be_attached screen shot) I'll also attach a vm snapshot.
Created attachment 62377 [details] screen shot
Created attachment 62378 [details] vm snapshot
The tab/config in question belongs to PDE.
Brian, can you please figure out where the bottleneck is and report back? I suspect the time is spent in 1. populating the product/application combo boxes and/or 2. populating the plug-ins viewer on the Plug-ins tab.
Eric, do you have any PDE project's in your workspace? I am hoping the answer it no :) From your JVM snapshot, it appears that PDE never initialized. This is consistent with the scenario of a workspace not containing any PDE projects. The downside is that for PDE to initialize, it needs to read the models in your target platform. Without that information, PDE would be much less useful. The time you are spending is actually the reading of the target platform, which by default is pointing to itself (and since RAD is huge, it takes more time). I would suspect that you see this problem only after the first time you open up the launch config after a restart. The subsiquent openings of the debug dialog go much quicker. Please let me know if my guesses are correct.
(In reply to comment #5) Brian, my answers below. Any further help needed, just let me know. > Eric, do you have any PDE project's in your workspace? I am hoping the answer > it no :) --> no pde project in this wks > I would suspect that you see this problem only after the first time you open up > the launch config after a restart. The subsiquent openings of the debug dialog > go much quicker. --> correct
Unfortunately, there is not much we can do. The Eclipse Application launch configuration needs plug-in information from the target platform. If the target platform has not yet been parsed (PDE has not yet needed to), then upon opening the launch configuration PDE will parse the target platform. It is this parsing that is causing the hold up. It does not make sense to run this in the background because the plug-in information is valuable to the user. The user would be able to click finish without seeing the plug-ins they will run with. The user would them still have to wait for PDE to complete the parsing before the Eclipse Application would launch, still causing the delay. Since this delay only happens once and if the user does not have any plug-in projects in the workspace, this will require a lot of investigation and work to solve a problem which is more inconvenient than problematic.
