Bugzilla – Full Text Bug Listing
| Summary: | deadlock with auto-complete | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Jurgen Vinju <jurgen.vinju> | ||||||
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||||
| Severity: | major | ||||||||
| Priority: | P3 | CC: | mauromol, stephan.herrmann | ||||||
| Version: | 4.7.3 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Mac OS X | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 276607 [details]
second stack trace with the same locking threads
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 *** Thanks. I've been trying to reproduce the issue but it comes and goes. I'll try the later version as well. |
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!