Bug 17197

Summary:	F1 - "Add Jars" to build path locks up eclipse - win2k
Product:	[Eclipse Project] JDT	Reporter:	Geoff Longman <glongman>
Component:	Core	Assignee:	David Audel <david_audel>
Status:	VERIFIED WORKSFORME	QA Contact:
Severity:	major
Priority:	P3
Version:	2.0
Target Milestone:	2.0 F2
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Geoff Longman

2002-05-23 08:05:08 EDT

I just installed F1, created a project with /src and /bin dirs.

Outside of eclipse I copied some src into /src and some jar files into the 
project root. Then I refreshed the project.

Then I right clicked on the project, select Properties -> Java BuildPath 
and "Add Jars". Selected a few, hit ok and Eclipse goes on to recompile the src.

The progress bar shows no progress , the compile never completes, and now 
eclipse is locked up.

I killed the Eclipse VM and restarted. The added Jars are there and everything 
is fine.

Comment 1 Erich Gamma

2002-05-25 07:14:53 EDT

moving to JDT CORE

Comment 2 Philipe Mulet

2002-05-25 08:28:47 EDT

Geoff - could you launch with console opened (using -vm .../java.exe) and press 
ctrl-break when the deadlock is occurring ?

This would point at the offending code.

Comment 3 Geoff Longman

2002-05-25 08:37:05 EDT

You mean from the command line? I've never done this.
Can you supply some pointers? Thanks

Comment 4 Philipe Mulet

2002-05-25 09:13:27 EDT

Launch eclipse with the following command line, where you supply <JDK> and 
<WORKSPACE> folder names.

D:\eclipse\sdk\eclipse\eclipse.exe -vm <JDK>\jre\bin\java.exe -data 
<WORKSPACE> -refresh -debug -consoleLog -vmargs -verify -Xms100Mb -Xmx200Mb

This will ensure a Java console is opened while Eclipse is up and running. At 
any point while running, you can select the Java console and press ctrl-break 
so as to get a stack dump of its activity, which then we would need in order to 
see what is going on...

Note (just in case <g>): if you left click in the console, it will freeze 
Eclipse, you can unfreeze why pressing any key or right clicking.

Comment 5 Geoff Longman

2002-05-25 09:37:43 EDT

Gosh guys, I can't reproduce it.

Using a fresh install of F1 and a new workspace:


Q:\eclipseF1_BUG\eclipse.exe -vm C:\jdk1.3.1_01\jre\bin\java.exe -data 
Q:\eclipseF1_BUG\test_workspace -refresh -debug -consoleLog -vmargs -verify -
Xms100Mb -Xmx200Mb


I also tried it in the default workspace in the new install:

Q:\eclipseF1_BUG\eclipse.exe -vm C:\jdk1.3.1_01\jre\bin\java.exe -data 
Q:\eclipseF1_BUG\workspace -refresh -debug -consoleLog -vmargs -verify -
Xms100Mb -Xmx200Mb

Again, can't reproduce. I do "Add Jars" and everthing proceeds normally.

Sorry,

Comment 6 Philipe Mulet

2002-05-27 06:04:51 EDT

No problem, will close. Please reopen if you can find some reproduceable steps.

Comment 7 David Audel

2002-06-03 09:12:21 EDT

Verified.