Bugzilla – Full Text Bug Listing
| Summary: | Java Editor Content Assist causes indefinite hang | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Niccolo Machiavelli <Uncle.Niccolo> | ||||
| Component: | Text | Assignee: | JDT-Text-Inbox <jdt-text-inbox> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | daniel_megert, remy.suen | ||||
| Version: | 3.7 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Please attach a VM dump, for details see http://wiki.eclipse.org/index.php/How_to_report_a_deadlock Created attachment 174471 [details]
Thread Dump in hung state
The threaddump-*.tdump contains the stack traces of all threads of eclipse after the typing of "." triggered the search for suggestions in the editor
I also made a fresh install of eclipse (same version) and my usual plugins on another machine. There the problem does not show itself, though I do not know what is different between the two installation.
Comment on attachment 174471 [details] Thread Dump in hung state Looks like it might be that Texlipse bug again. See bug 319098. *** This bug has been marked as a duplicate of bug 319098 *** |
Build Identifier: 20100617-1415 (64 bit Mac OS X Cocoa) When editing a Java file, as soon as the syntax completion is triggered (by the . character) the beach ball of death appears and does not disappear again. Reproducible: Always Steps to Reproduce: 1. Start Eclipse for a new Java project 2. Create new source file with class containing main. 3. Try to add "System.out.println("Hello World!);" to main method As soon as "System." ist typed, eclipse hangs - it can only be terminated by killing the process. Everything works if "Enable auto activation" is unchecked in the Java->Editor->Content Assist Preferences, but of course, then there is no help showing the available methods for a class.