Community
Participate
Working Groups
Build Identifier: M20100211-1343 When working with Eclipse it sometimes crashes. The console tells me: 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 194489 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.) Reproducible: Sometimes Steps to Reproduce: Just happens - although it doesn't take too much to get it crashing.
What JVM are you using? How did you install Eclipse? What file did you download? What is its name? What versions of GTK+ do you have installed on your system? What distro are you on? What versions of Firefox/XULRunner are you on?
I'm running Ubuntu lucid 64. Eclipse is set to use java-sun-6 (since I'm not sure whether the performance bug with openjdk is still present). I downloaded the recent eclipse from the download site - since the Ubuntu version is freezing on me all the time. GTK version is 2.20. Firefox is 3.6.3/XULRunner is 1.9.1 and 1.9.2
Do you have GNOME Accessibility enabled?
(In reply to comment #3) > Do you have GNOME Accessibility enabled? Nope
(In reply to comment #2) > I'm running Ubuntu lucid 64. Eclipse is set to use java-sun-6 (since I'm not > sure whether the performance bug with openjdk is still present). Use (s)locate or some other tool to try and find hs_err_pid log files.
(In reply to comment #5) > (In reply to comment #2) > > I'm running Ubuntu lucid 64. Eclipse is set to use java-sun-6 (since I'm not > > sure whether the performance bug with openjdk is still present). > > Use (s)locate or some other tool to try and find hs_err_pid log files. Sorry I cannot find any of these files.
if you get javacore or hs_err_<pid> files, they'll be in the directory you launch your eclipse from. try this: $ java -version $ eclipse -data tmp_workspace -consoleLog PW
(In reply to comment #7) > if you get javacore or hs_err_<pid> files, they'll be in the directory you > launch your eclipse from. > > try this: > > $ java -version java version "1.6.0_19" Java(TM) SE Runtime Environment (build 1.6.0_19-b04) Java HotSpot(TM) 64-Bit Server VM (build 16.2-b04, mixed mode) > $ eclipse -data tmp_workspace -consoleLog Starts - when I attemt to close the initial "wizard" frame I get 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 10780 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.) BTW: I'm using gnome-shell/mutter so it might be that any dirty trick that you had working with metacity or the like does not work anymore.
(In reply to comment #8) > (In reply to comment #7) > > $ eclipse -data tmp_workspace -consoleLog > Starts - when I attemt to close the initial "wizard" frame I get > 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 10780 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.) Afterwards running just with -consoleLog I get: !SESSION 2010-04-21 12:02:43.204 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_20 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product -consoleLog !ENTRY org.eclipse.core.resources 2 10035 2010-04-21 12:02:53.042 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes. 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 121821 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.)
*** Bug 309929 has been marked as a duplicate of this bug. ***
I found a similar bug in the Debian BTS: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571192 Going to try to upgrade Cairo and see if that solves the problem.
(In reply to comment #11) > I found a similar bug in the Debian BTS: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571192 > > Going to try to upgrade Cairo and see if that solves the problem. On Ubuntu Lucid there is already 1.8.10-2 installed.
(In reply to comment #12) > (In reply to comment #11) > > I found a similar bug in the Debian BTS: > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571192 > > > > Going to try to upgrade Cairo and see if that solves the problem. > On Ubuntu Lucid there is already 1.8.10-2 installed. Yes, but according to the Debian ticket, this bug is not fixed until 1.9.6, which is not in Ubuntu Lucid. I haven't managed to build this version on Lucid either, so I'm not sure if it would fix the problem, but it would be worth a try.
When re-reading the Debian issue, I found that the solution was to file bugs against the other packages that had the same issues, so upgrading cairo will not solve anything, but the bug seems to reside in Eclipse and/or its other dependencies.
I'm also experiencing this issue, running Lucid bdavis@leoben:~/java/eclipse$ java -version java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode) I'm running with the console logging turned on to try to gather more information
(In reply to comment #15) > I'm also experiencing this issue, running Lucid > > bdavis@leoben:~/java/eclipse$ java -version > java version "1.6.0_20" > Java(TM) SE Runtime Environment (build 1.6.0_20-b02) > Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode) > > I'm running with the console logging turned on to try to gather more > information While running Ubuntu 10.04 (Lucid Lynx) I've had a similar experience with crashing due to a bug in libcairo. According to the maintainer, a more recent version of libcairo2 resolves the issue and after testing it seems to be the case for me. The experimental repo is located here: http://packages.debian.org/experimental/libcairo2 . There are versions for most of Ubuntu's supported arches and it should be fairly compatible, since Ubuntu is an upstream release of Debian. There is one caveat so far however, I've noticed the quality of font rendering has degraded slightly after installing the experimental version. It's not unusable or lacking AA, but it's noticeably less crisp.
(In reply to comment #16) > (In reply to comment #15) > > I'm also experiencing this issue, running Lucid > > > > bdavis@leoben:~/java/eclipse$ java -version > > java version "1.6.0_20" > > Java(TM) SE Runtime Environment (build 1.6.0_20-b02) > > Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode) > > > > I'm running with the console logging turned on to try to gather more > > information > > While running Ubuntu 10.04 (Lucid Lynx) I've had a similar experience with > crashing due to a bug in libcairo. > > According to the maintainer, a more recent version of libcairo2 resolves the > issue and after testing it seems to be the case for me. The experimental repo > is located here: http://packages.debian.org/experimental/libcairo2 . There are > versions for most of Ubuntu's supported arches and it should be fairly > compatible, since Ubuntu is an upstream release of Debian. > > There is one caveat so far however, I've noticed the quality of font rendering > has degraded slightly after installing the experimental version. It's not > unusable or lacking AA, but it's noticeably less crisp. I'm sorry, please disregard that report, I've had a crash with the latest experimental version as well. I'm going to try to downgrade libcairo to an older version.
(In reply to comment #14) > When re-reading the Debian issue, I found that the solution was to file bugs > against the other packages that had the same issues, so upgrading cairo will > not solve anything, but the bug seems to reside in Eclipse and/or its other > dependencies. Removing xulrunner solved the problem for me. I haven't spent any time investigating why this fixes the problem, and I don't have any other applications that require xulrunner so this was an ok solution for me. Hopefully someone with the time and will to investigate can use this information for something useful.
*** Bug 311378 has been marked as a duplicate of this bug. ***
Why is this bug not in the SWT bucket? Dup of bug 308731 and bug 303372?
*** This bug has been marked as a duplicate of bug 303372 ***
