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

Bug 508707

Summary:

Eclipse/Java does not shut down looping JTests

Product:

[Eclipse Project] JDT

Reporter:

Eric Wells <epiqu1n>

Component:

Debug

Assignee:

JDT-Debug-Inbox <jdt-debug-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

jarthana, sarika.sinha

Version:

3.1

Target Milestone:

---

Hardware:

Macintosh

OS:

Mac OS X

URL:

http://imgur.com/a/HhKUQ

Whiteboard:

stalebug

Attachments:

Description	Flags
Heap dump	none

Description Eric Wells

2016-12-05 19:11:00 EST

When running JTests, if there is a loop present in the code being tested and no Timeout has been defined, the code will run indefinitely.  Upon trying to stop the tests, the UI will display "Stopping..." but never actually stop the test, causing each instance of this to continue running and use an entire CPU core (and a lot of energy) until either Eclipse is exited or the Java processes are stopped through Activity Monitor.

-- Configuration Details --
Product: Eclipse 4.6.0.20160613-1800 (org.eclipse.epp.package.java.product)
Installed Features:
 org.eclipse.jdt 3.12.0.v20160606-1100

Comment 1 Jay Arthanareeswaran

2016-12-05 23:32:45 EST

I am not sure what might be happening. Copying Sarika for response.

Comment 2 Sarika Sinha

2016-12-06 00:22:49 EST

@Eric,
Can you provide any log, call stack or memory dump to confirm that Eclipse is Contributing to this and not JTest ?

Comment 3 Eric Wells

2016-12-06 12:04:45 EST

Where would I find one of those?

Comment 4 Sarika Sinha

2016-12-06 23:16:16 EST

(In reply to Eric Wells from comment #3)
> Where would I find one of those?

You can find the last stacktrace in Error Logs View.

For getting dump, you can refer to
https://wiki.eclipse.org/How_to_report_a_deadlock

Comment 5 Eric Wells

2016-12-08 11:46:15 EST

There are no errors in the error log when this happens.  I just noticed that if I click the stop button in the JUnit window, it will go gray and display "Stopping..." (as in the image I linked to originally), but will not actually stop it.  However, if I click the stop button that is in the console view, it does actually terminate the program.

Comment 6 Eric Wells

2016-12-08 12:41:30 EST

Created attachment 265781 [details]
Heap dump

Comment 7 Sarika Sinha

2016-12-09 08:28:45 EST

(In reply to Eric Wells from comment #6)
> Created attachment 265781 [details]
> Heap dump

Can't get any help from this as it does not tell the threads which were active at that time.

Comment 8 Eclipse Genie

2020-02-23 14:14:39 EST

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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.