openjdk team mailing list archive

[Ichthyostega <prg@xxxxxxxxxxxxxxx>]

Public bug reported:

Eclipse crashes on each attempt of picking an autocompletion proposal.
Showstopper.

I am test driving Ubuntu Lucid since three weeks. Got this error occasionally. But since the last round of updates (since end of last week, which I installed yesterday) it happens reproducible. Restarting X doesn't help.
For an autocompletion proposal, Eclipse creates an hovering window next the text cursor. The crash happens when this window is disposed (either by picking a proposal with mouse or keypress, or by just closing it by pressing ESC or clicking outside). At that point, the space occupied of the window remains black for about 0.2 sec, (which is abnormal; usually this space is filled with the current background colour). Then App Windows get destroyed; console output:

> 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 80834 error_code 161 request_code 149 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.)

I am running a TwinView on a NVidia card, using the nouveau driver.

** Affects: openjdk-6 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Java Eclipse killed by X error
https://bugs.launchpad.net/bugs/570945
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-6 in ubuntu.

Status in “openjdk-6” package in Ubuntu: New

Bug description:
Eclipse crashes on each attempt of picking an autocompletion proposal. Showstopper.

I am test driving Ubuntu Lucid since three weeks. Got this error occasionally. But since the last round of updates (since end of last week, which I installed yesterday) it happens reproducible. Restarting X doesn't help.
For an autocompletion proposal, Eclipse creates an hovering window next the text cursor. The crash happens when this window is disposed (either by picking a proposal with mouse or keypress, or by just closing it by pressing ESC or clicking outside). At that point, the space occupied of the window remains black for about 0.2 sec, (which is abnormal; usually this space is filled with the current background colour). Then App Windows get destroyed; console output:

> 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 80834 error_code 161 request_code 149 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.)

I am running a TwinView on a NVidia card, using the nouveau driver.