Bug 172254 - Autocomplete showing "Internal error" and freezing
Summary: Autocomplete showing "Internal error" and freezing
Status: VERIFIED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.3 M5   Edit
Assignee: David Audel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-30 19:44 EST by Ben Bucksch CLA
Modified: 2007-02-05 11:23 EST (History)
0 users

See Also:


Attachments
Screenshot of freeze (39.11 KB, image/png)
2007-01-30 19:45 EST, Ben Bucksch CLA
no flags Details
Testcase, not minimized. (58.23 KB, application/zip)
2007-01-30 19:47 EST, Ben Bucksch CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Bucksch CLA 2007-01-30 19:44:06 EST
Build ID: M20060629-1905

Steps To Reproduce: (100% reproducable for me)
1. Unzip attached project (sorry, I don't know what in there causes it)
2. Open extracted source as workbench path
3. There is no eclipse .metadata yet, so Eclipse will create it 
4. Go to Workbench.
5. File|New|Project|Java Project
6. Enter "Recorder" as project name, "Create in workbench". There is an existing directory with that name, and it has a .project and .classpath.
7. Recorder project with existing source will be added to workbench
8. Go to package core, Scheduler.java
9. Create a new empty line before "myTimers.put(id, timer);"
10. Type "timer."
11. Possibly press space for autocomplete, or just wait a moment

Actual result:
Autocomplete scrolling listbox popup shows up.
Only line 1 and 4 are filled out, the rest of the lines are grey.

This state stays until I move the mouse over the popup. Then, the following happens:

Some (all but 2) of the other lines are filled out.

Two "Internal error" windows show up. They contain text, but are underneat the popup, so cannot be read.

The autocomplete popup stays on top of all windows, even from other apps.

Eclipse stops drawing, so I cannot move the error windows to front and read the text, because they'll be grey. Nothing in Eclipse draws anymore. It does not react at all. Clicking the [x] of the KDE window manager does not close Eclipse, not even the non-responding detection (to allow a kill) works anymore, need to "killall java".

Testcase:
The same source worked fine before I wiped my eclipse metadata.
I am not sure whether the method of project creation is a factor. Even if that's the wrong way to import, it's still a bug.
Sorry that I can't narrow the bug down further, but I have no idea what causes it.
Comment 1 Ben Bucksch CLA 2007-01-30 19:45:10 EST
Created attachment 57877 [details]
Screenshot of freeze
Comment 2 Ben Bucksch CLA 2007-01-30 19:47:54 EST
Created attachment 57878 [details]
Testcase, not minimized.

This is my project's source where the problem appears.

Legal note: I post the source merely for the reproduction of this bug. This shall not represent a publication of the source. Ignore any open-source licenses in there, I do not license it.
Comment 3 Ben Bucksch CLA 2007-01-30 19:53:47 EST
java version "1.5.0_10"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_10-b03, mixed mode)

That's also what the project uses.
Comment 4 Olivier Thomann CLA 2007-01-30 20:29:41 EST
You are using Eclipse 3.2.
Could you please try again using the latest 3.2.2 build (M20070125-1400) ?
I don't get any failure using that build.
Comment 5 Ben Bucksch CLA 2007-02-01 18:52:32 EST
I updated to 3.2.1 (linked from "Download" page) and don't see the bug anymore.

Closing INVALID.

Will reopen in case I see it again, but it seems it was already fixed. Sorry.