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

Bug 338172

Summary: "X Window System error" "RenderBadPicture" crash when using content assist popups
Product: [Eclipse Project] Platform Reporter: Ian Wood <subscriptions>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: critical    
Priority: P3 CC: daniel_megert, eclipse.felipe, grant_gayed, remy.suen
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
Another console output none

Description Ian Wood CLA 2011-02-24 21:35:35 EST
Build Identifier: M20100909-0800

When I use content assist to fill in a field from a particular class, eclipse crashes with a "X Window System error" "RenderBadPicture". 

This may be related to these bugs:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=303372
https://bugs.eclipse.org/bugs/show_bug.cgi?id=319232

I have tried some other classes, and the crash doesn't happen. With the offending class, it happens every time however.

Below is a typical output from the console:

Start VM: -Xms40m
-Xmx384m
-XX:MaxPermSize=256m
-Djava.class.path=/scratch/bin/eclipse//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-os linux
-ws gtk
-arch x86
-showsplash /scratch/bin/eclipse//plugins/org.eclipse.platform_3.6.1.v201009090800/splash.bmp
-launcher /scratch/bin/eclipse/eclipse
-name Eclipse
--launcher.library /scratch/bin/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.1.R36x_v20100810/eclipse_1309.so
-startup /scratch/bin/eclipse//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-consolelog
-showlocation
-debug
-vm /usr/lib/jvm/java-6-sun-1.6.0.20/jre/bin/../lib/i386/client/libjvm.so
-vmargs
-Xms40m
-Xmx384m
-XX:MaxPermSize=256m
-Djava.class.path=/scratch/bin/eclipse//plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar 
Install location:
    file:/scratch/bin/eclipse/
Configuration file:
    file:/scratch/bin/eclipse/configuration/config.ini loaded
Configuration location:
    file:/scratch/bin/eclipse/configuration/
Framework located:
    file:/scratch/bin/eclipse/plugins/org.eclipse.osgi_3.6.1.R36x_v20100806.jar
Framework classpath:
    file:/scratch/bin/eclipse/plugins/org.eclipse.osgi_3.6.1.R36x_v20100806.jar
Splash location:
    /scratch/bin/eclipse//plugins/org.eclipse.platform_3.6.1.v201009090800/splash.bmp
Debug options:
    file:/home/drevicko/workspace-psycholingua/psycholingua/.options not found
Time to load bundles: 4
Starting application: 664
!SESSION 2011-02-25 12:30:24.129 -----------------------------------------------
eclipse.buildId=M20100909-0800
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_AU
Framework arguments:  -showlocation
Command-line arguments:  -os linux -ws gtk -arch x86 -consolelog -showlocation -debug

!ENTRY org.eclipse.ui 4 4 2011-02-25 12:30:28.165
!MESSAGE Unable to associate action set with part: org.eclipse.jdt.ui.CompilationUnitEditor. Action set org.codehaus.groovy.eclipse.junit.JUnitActionSet not found.
Application Started: 4554

!ENTRY org.eclipse.ui 4 4 2011-02-25 12:30:41.435
!MESSAGE Unable to associate action set with part: org.eclipse.jdt.ui.PackageExplorer. Action set org.codehaus.groovy.eclipse.junit.JUnitActionSet not found.
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 76769 error_code 158 request_code 148 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.)


Reproducible: Always

Steps to Reproduce:
1. Run eclipse
2. Open an editor that does not contain the offending class, but "import"s it
3. Type the class name and a period "." 
4. Select one of the class fields (enter or double click)
5. Eclipse crashes without a stack trace
Comment 1 Ian Wood CLA 2011-02-24 21:36:43 EST
Created attachment 189769 [details]
Another console output
Comment 2 Dani Megert CLA 2011-02-25 01:47:53 EST
Did you try to install the latest XUL runner version?

>I have tried some other classes, and the crash doesn't happen. With the
>offending class, it happens every time however.
The problem is not directly the class but the proposals that are shown when you invoke content assist on that class.

I assume you're in the Java editor?

Moving to SWT for investigation.
Comment 3 Ian Wood CLA 2011-03-03 01:50:24 EST
(In reply to comment #2)

An update on the behaviour of this bug: It seems to be related to removing the javadoc popup that appears next to the content assist popup: 

Where there is no javadoc popup for some method/field etc.., it doesn't seem to crash. 

If there is a javadoc popup and I spell eg a method wrong, type a whole method name or double click a method, it crashes - I imagine that all these things normally result in both popups disappearing.

> Did you try to install the latest XUL runner version?

To be honest, I'm not entirely sure - this is a work machine not managed by me..
Is there an easy way to find out?

> I assume you're in the Java editor?

yes
Comment 4 Ian Wood CLA 2011-03-03 01:54:04 EST
(In reply to comment #3)

I forgot to mention:  If I save the file (ctrl-S), the popups (suggestions and javadoc) disappear harmlessly. 

I'm using this as a workaround, though sometimes I forget ):
Comment 5 Ian Wood CLA 2011-04-04 09:45:23 EDT
Updating to the latest xulrunner (1.9.2) from (1.9.1.??) fixed the problem.

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