541297 – deadlock with auto-complete

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

Bug 541297 - deadlock with auto-complete

Summary: deadlock with auto-complete

Status:	CLOSED DUPLICATE of bug 539685

Alias:	None

Product:	JDT
Classification:	Eclipse Project
Component:	Core (show other bugs)
Version:	4.7.3
Hardware:	PC Mac OS X

Importance:	P3 major (vote)
Target Milestone:	---
Assignee:	JDT-Core-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2018-11-19 05:05 EST by Jurgen Vinju
Modified:	2018-11-19 11:58 EST (History)
CC List:	2 users (show)

See Also:

Attachments
jstack output on non-responsive Eclipse (20.11 KB, application/octet-stream) 2018-11-19 05:05 EST, Jurgen Vinju	no flags	Details
second stack trace with the same locking threads (19.10 KB, application/octet-stream) 2018-11-19 05:05 EST, Jurgen Vinju	no flags	Details
View All 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 Jurgen Vinju

2018-11-19 05:05:16 EST

Created attachment 276606 [details]
jstack output on non-responsive Eclipse

This is the third time I run into a deadlock situation the last months, and I seem to recall it involved auto-complete everytime. Also and perhaps this is accidental I was auto-completing some Java streams code.

Please find to stack traces acquired with `jstack`, taken briefly after one another (one minute between) on the Eclipse instance which wasn't responding any longer. I realize this bug must be very hard to reproduce.

Thanks!

Comment 1 Jurgen Vinju

2018-11-19 05:05:55 EST

Created attachment 276607 [details]
second stack trace with the same locking threads

Comment 2 Stephan Herrmann

2018-11-19 11:02:40 EST

Please try with release 4.9 (2018-09) to see if this is fixed via bug 473654.

Otherwise judging by stack traces this likely is the same as bug 539685.

If you have a reproducing example this would still be welcome (please add it to bug 539685).

*** This bug has been marked as a duplicate of bug 539685 ***

Comment 3 Jurgen Vinju

2018-11-19 11:22:49 EST

Thanks. I've been trying to reproduce the issue but it comes and goes. I'll try the later version as well.