Community
Participate
Working Groups
This bug was created in response to 84606. To reproduce the bug you will first need a CDT project with a large code base. I'm using Ethereal (http://www.ethereal.com/download.html) as a test project for this bug. First create a project that points to the Ethereal source code before following these instructions to reproduce the bug. Instructions to reproduce the bug: 1) download/extract Eclipse 3.1M6 (http://www.eclipse.org/downloads/) 2) download/extract CDT 3.0M6 candidate (in same directory as Eclipse) (http://fullmoon.rtp.raleigh.ibm.com/tools/cdt/builds/3.0.0/I.I200504110306/inde x.html) 3) start Eclipse + CDT in a new workspace 4) create a new Standard Make C++ Project (don't need source files) 5) import a project with a large code base (such as the Ethereal project mentioned above) A screenshot is attached. My computer says that ~0-3% CPU is being used when Eclipse is frozen as shown in the screenshot. The "Import Projects" dialog is still displayed and it can't be canceled/closed. Clicking Cancel disables the cancel button. Clicking the 'X' to close the dialog displays the error "Wizard can not be closed due to an active operation. You must cancel the operation before you can close the wizard." Interesting Note: I can't seem to reproduce the bug without first creating a C/C++ project before importing the project with a large code base.
Created attachment 19777 [details] Screenshot of the bug.
Please review this bug and let me know if it is the same bug that you reported for PR https://bugs.eclipse.org/bugs/show_bug.cgi?id=84606. I have a feeling that this is a new bug. Thanks, Devin
Alain, If you get a minute can you look into this and give your thoughts? It seems to be related to auto-build and the Eclipse "Import Projects" dialog. Thanks, Devin
Update: I can only reproduce this bug when the imported large project has auto build turned on.
(In reply to comment #3) > Alain, > If you get a minute can you look into this and give your thoughts? It seems to > be related to auto-build and the Eclipse "Import Projects" dialog. Almost missed this. Well, there is a lot going on. In Eclipse-3.1 now, even if the import is batch whitin a WorkspaceRunnable From time to time during the import the ResourceDelta is trigger(this is done by the platform to show some responsiveness) ... which triggers: - an auto-build - the indexer via the CElementDelta event - trigger the Auto-discovery - trigger pathEntry markers etc .. There are different strategies to deal with this but I agree for scalability ... it's not good.
Used CDT 3.0.0 Build I200504131010. Well, I try to import 3 existing mgd make cpp projects all together into my workspace, it just simple doesn't work. It keeps running for 10 minutes. The Import dialog is always presented and cancel doesn't work. You can see "Refreshing workspace" on the right corner of workbench. Only thing I can do is to kill the IDE. All these project are indexer turned on. The zip file of projects and screen shot are attached.
Created attachment 19871 [details] zip file of 3 projects Unzip them into your workspace and import existing project, choose all of them and import.
Created attachment 19873 [details] zip file of screenshot of Importing existing project
I have been unable to reproduce this bug with Eclipse 3.1M6 (I20050401-1645) and CDT 3.0M6 (200504140301). I am still seeing Bug 84606.
Future means you commit to fix it in the Future. Inboxes can't make committments. Moving to '--'.
