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

Bug 319271

Summary: Eclipse crashes with RenderBadPicture (invalid Picture parameter)
Product: [Eclipse Project] JDT Reporter: Brad Jackson <brad.jackson>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: critical    
Priority: P3    
Version: 3.5.2   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Brad Jackson CLA 2010-07-08 10:04:33 EDT
Build Identifier: 20100218-1602

Using auto-complete when editing a Java file has started crashing Eclipse. I just did a distro upgrade and the crash started after that, so that may be related.

Eclipse 3.5.2
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
Linux distro: Mandriva 2010.1 64-bit, upgrade from 2010.0

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 27022 error_code 161 request_code 150 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. Edit a Java file
2. Put the cursor after a PreparedStatement object
3. Press Ctrl+Space for the auto-complete popup
4. Press Enter or Esc

Doesn't appear to crash when auto-completing user-defined classes.
Comment 1 Brad Jackson CLA 2010-07-08 10:07:46 EDT

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