Bug 55859 - 'unbound classpath container' trigger infinite loops
Summary: 'unbound classpath container' trigger infinite loops
Status: CLOSED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1.2   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2004-03-24 05:43 EST by Gilles Scokart CLA
Modified: 2009-08-30 02:05 EDT (History)
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 Gilles Scokart CLA 2004-03-24 05:43:51 EST 
I use version 2.1.3.

I created a new workspace
I made a copy of an old project directly into my workspace.  This project was
using a 'JRE 1.3'.  But this JDK name was not yet defined in my workspace.

When I have ask to create a project using the name of the project I just copied,
the wizard deteced that the project was created, and analyzed the content.

I clicked on Finish, then eclipse started to use 100% of the CPU.  I guess it's
the incremental builder that was looping.

In the task list, I have seen an 'unbound classpath container' error because the
JRE 1.3 was not known.

It took me +/- 10 minutes to manage to close the project, then the CPU stopped
to be used.
Comment 1 Philipe Mulet CLA 2004-03-24 06:13:00 EST 
Please provide a thread dump so as to identify the offending piece of code.
Start Eclipse with console open, and press ctrl-pause to force VM to dump its 
activity.
Comment 2 Philipe Mulet CLA 2004-03-25 09:53:15 EST 
Please reopen once information is available
Comment 3 Frederic Fusier CLA 2005-02-17 09:36:52 EST 
Closing as never reproduced in a long time
Comment 4 Denis Roy CLA 2009-08-30 02:05:09 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.