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

Bug 444042

Summary:

Eliplse goes into endless loop when trying to terminate

Product:

[Eclipse Project] JDT

Reporter:

Larry Johnson <Larry.Johnson>

Component:

Core

Assignee:

JDT-Core-Inbox <jdt-core-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

jarthana, stephan.herrmann

Version:

4.4

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

stalebug

Attachments:

Description	Flags
Additional info: the file javaw.mail.jar was destroyed by Eclipse	none

Description Larry Johnson

2014-09-14 06:27:05 EDT

Hello,
I am using Luna M6 Release (4.4.0M6).

I was testing the Oracle program to create shapes:  http://docs.oracle.com/javase/tutorial/2d/geometry/arbitrary.html

The program worked. I then tried to make an affinetransform translate the shape to a new location.

I noticed the red button indicating that some previous program was still executing in Eclipse. I tried several times to terminate, but the button remained red.

I then clicked the upper right Eclipse button to terminate Eclipse. It started to shutdown. The window "Saving Workspace" came up. The green bar quickly moved to about the position of "or" in the message "Saving Workspace". I remained there for over an hour without making further progress.

I then forced Eclips to terminate using the Task Manager. This worked okay.

I then restarted Eclipse. It started up okay. I then tried to launch the program that had previously executed. I received the error message: "Could not find or load the class -- class name".

I added a comment to the source file and saved it -- attempting to force a rebuild. I attempted to launch the program again -- the same error message.

I then launched the same program without change with NetBeans and everything worked.

I filed a Bug report a few weeks ago about not being able to compile Java programs that were previously running. I believe that this is additional info with respect to the same basic problem.

Irrespective of this particular problem, there should be a capability in Eclipse to force a shutdown and restore the Elipse database to a usable state, even if it means some of the last edits are lost. In my case, the edits are not lost -- it is only the linkage to the compiled class files.

Thank you.

Best regards,

Larry Johnson

Comment 1 Stephan Herrmann

2014-09-14 06:46:33 EDT

There's two parts to this:

Launching / terminating is handled in the JDT/Debug component.
But I doubt that the above information suffices to work on this.
For starters you should probably investigate the state where the terminate button doesn't seem to have effect. Is your application still running?
(Use the TaskManager to find out, perhaps use jvisualvm to find out its
internal state / take thread dumps).
If you have interesting information from this investigation please file
a bug against JDT/Debug.


Regarding the issue of "Could not find or load the class ...": please check the content of your project's output folder (normally "bin") and see if it contains
the .class files of your application.

Comment 2 Stephan Herrmann

2014-09-14 06:49:20 EDT

Forgot this part:

(In reply to Larry Johnson from comment #0)
> I then clicked the upper right Eclipse button to terminate Eclipse. It
> started to shutdown. The window "Saving Workspace" came up. The green bar
> quickly moved to about the position of "or" in the message "Saving
> Workspace". I remained there for over an hour without making further
> progress.

Particularly in this state one or more stack dumps would be helpful.
Please see http://wiki.eclipse.org/How_to_report_a_deadlock

Comment 3 Larry Johnson

2014-09-14 11:44:53 EDT

Created attachment 247049 [details]
Additional info: the file javaw.mail.jar was destroyed by Eclipse

Hello,

Eclipse termination locked up again today and some more files that were executable stopped functioning (no class file and they would not recompile to produce a class file).

I switched over to NetBeans. This time it also had a problem. It said that the file "javaw.mail.jar" was missing and gave me a file browser to try to find another copy. I found a Java 1.7 version from a previous download. I selected it and NetBeans began to work.

I switched back to Eclipse and the Java files that I was just working with began to behave normally in Eclipse. I don't know if this resolved all of the Eclipse execution problems -- there is close to 1000 to check.

It would appear that for some reason, Eclipse destroyed this file "javaw.mail.jar". The only things that I had been doing were Java file edits and   Run for testing.

I hope this is helpful.

Best regards,

Larry Johnson

Comment 4 Stephan Herrmann

2014-09-14 11:55:48 EDT

(In reply to Larry Johnson from comment #3)
> It would appear that for some reason, Eclipse destroyed this file
> "javaw.mail.jar". The only things that I had been doing were Java file edits
> and   Run for testing.
> 
> I hope this is helpful.

Sorry, but all this is way too vague to even start working on it.
If you have evidence that Eclipse destroyed a file please provide steps that trigger this.

Comment 5 Eclipse Genie

2019-08-19 00:50:45 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.