Community
Participate
Working Groups
Build Identifier: M20100211-1343 Using Eclipse on Ubuntu 10.04, Eclipse deadlocks when trying to use autocompletion. Reproducible: Always Steps to Reproduce: 1. Install Eclipse on Ubuntu 10.04 2. Start a new Java project 3. Create a new Class 4. Type import java.util. and wait for autocomplete to pop up.
Created attachment 163053 [details] full thread dump
Sometimes, instead of a deadlock, Eclipse completely crashes with the following error: The program 'Eclipse' received an X Window System error. This probably reflects a bug in the program. The error was 'RenderBadPicture (invalid Picture parameter)'. (Details: serial 54675 error_code 172 request_code 152 minor_code 7) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) These errors occur regardless of compiz being enabled or not.
I don't know much about this stuff, but it looks like it's getting stuck in trying to resolve your browser. You could try googling how to hook up the browser correctly and that might get you going. Of course this should not deadlock, but that's another matter.
Looks like this might be a duplicate of this bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=303372 and this one: https://bugs.eclipse.org/bugs/show_bug.cgi?id=304718 Using the xulrunner workaround in #304718 fixes the problem. Should I mark this as a duplicate?
Yes, Adam, looks like bug 304718 is the same. Thanks for tracking this down. *** This bug has been marked as a duplicate of bug 304718 ***
