Community
Participate
Working Groups
Build Identifier: Eclipse randomly crashes when accessing [libpango-1.0.so.0] pango_context_get_matrix. There is no specific time or cause to this as far as I'm aware. Reproducible: Sometimes Steps to Reproduce: Use the platform for any amount of time. Randomly it will crash the who platform and not save the workbench settings.
Created attachment 175419 [details] Crash Log
I believe this is a bug GTK itself. Check the stack, all the SWT code did was to dispatch an event. The error occured in event handler interal to GTK. Silenio, do you agree or am I missing something ?
Agree. What version of gtk and pango are you running? What distribuition?
I'm running CentOS 5.5 (Final) Kernel: Linux bfitzger-linux 2.6.18-194.8.1.el5PAE #1 SMP Thu Jul 1 19:46:23 EDT 2010 i686 i686 i386 GNU/Linux Packages: pango-1.14.9-8 libgtk-java-2.8.7-3 gtk2-2.10.4-20 gtk+-1.2.10-56 Let me know if you need any more info. Brandon
we are also seeing this problem, crash is random. we build our xulrunner ( source of 1.9.2.10, JDK 1.6.0.13 used for xpcom) , and JRE1.6.0.13 is bundled with our application. Most of the time, everything works just fine, but sometimes when launch a browser from our app and pointing to a url ( google.com ), it crashes and have not able to reproduce it... Is this bug being investigated and when can we expect a fix? Please let me know if you need more information. OS:Red Hat Enterprise Linux Server release 5 (Tikanga) uname:Linux 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:21 EST 2007 i686 libc:glibc 2.5 NPTL 2.5 rlimit: STACK 10240k, CORE 0k, NPROC 32617, NOFILE 1024, AS infinity load average:0.70 0.40 0.16 CPU:total 2 (2 cores per cpu, 1 threads per core) family 6 model 7 stepping 10, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3 Memory: 4k page, physical 2066172k(330160k free), swap 2096472k(2096380k free) vm_info: Java HotSpot(TM) Client VM (11.3-b02) for linux-x86 JRE (1.6.0_13-b03), built on Mar 9 2009 01:29:45 by "java_re" with gcc 3.2.1-7a (J2SE release)
I experience this once or twice a day. It seems related but instead of reporting pango_context_get_matrix it states pango_context_load_font. Should I raise this a separate issue? # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x006122ae, pid=31692, tid=4159801552 # # JRE version: 6.0_21-b06 # Java VM: Java HotSpot(TM) Client VM (17.0-b16 mixed mode, sharing linux-x86 ) # Problematic frame: # C [libpango-1.0.so.0+0x122ae] pango_context_load_font+0x3e # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #
Created attachment 209488 [details] Crash log on CentOS5.5 Crash log for the latest crash.
I have seen this crash today . It is frequently crashing while opening a java file. Please help! Thanks
Is there any workaround for this issue?
i encounter crash everyday:( i am using eclipse 3.62. 32bit linux version. M20110210-1200 run on oracle linux 5. kernal: 2.6.18.238.0.0.0.1el5xen pls help! --------------the crash log # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x002cb9bf, pid=23338, tid=4159924432 # # JRE version: 6.0_31-b04 # Java VM: Java HotSpot(TM) Client VM (20.6-b01 mixed mode, sharing linux-x86 ) # Problematic frame: # C [libpango-1.0.so.0+0x129bf] pango_context_get_matrix+0x1f # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # --------------- T H R E A D --------------- Current thread (0x09f45800): JavaThread "main" [_thread_in_native, id=23338, stack(0xffd14000,0xffd64000)] siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0xffffffff Registers: EAX=0x09f34ed0, EBX=0x002f7100, ECX=0x0a10d360, EDX=0xf32ced60 ESP=0xffd61970, EBP=0xffd61988, ESI=0xffffffff, EDI=0x0a237968 EIP=0x002cb9bf, EFLAGS=0x00210286, CR2=0xffffffff Top of Stack: (sp=0xffd61970) 0xffd61970: 09f45920 00000000 0a237968 002cb9aa 0xffd61980: 00285b74 f32ced60 ffd61a88 00215a1b 0xffd61990: ffffffff 09f3deb0 ffd619c8 f36dd7e0 0xffd619a0: 0a237968 ffd619b0 ffd619b0 f36dd7aa 0xffd619b0: 00000000 00000000 00000000 00000000 0xffd619c0: 00000008 9901f658 ffd619f8 f5b6c2b9 0xffd619d0: 09f45920 0a238838 0a237968 ffd619e4 0xffd619e0: 00000001 00000001 9901f658 00db521e Instructions: (pc=0x002cb9bf) 0x002cb99f: 00 55 89 e5 56 53 e8 bd 60 ff ff 81 c3 56 b7 02 0x002cb9af: 00 83 ec 10 8b 75 08 e8 8d 4f ff ff 85 f6 74 0a 0x002cb9bf: 8b 16 85 d2 74 04 3b 02 74 10 89 44 24 04 89 34 0x002cb9cf: 24 e8 e3 55 ff ff 85 c0 74 0a 8b 46 18 83 c4 10 Register to memory mapping: EAX=0x09f34ed0 is an unknown value EBX=0x002f7100: <offset 0x3e100> in /usr/lib/libpango-1.0.so.0 at 0x002b9000 ECX=0x0a10d360 is an unknown value EDX=0xf32ced60 is an unknown value ESP=0xffd61970 is pointing into the stack for thread: 0x09f45800 EBP=0xffd61988 is pointing into the stack for thread: 0x09f45800 ESI=0xffffffff is an unknown value EDI=0x0a237968 is an unknown value Stack: [0xffd14000,0xffd64000], sp=0xffd61970, free space=310k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [libpango-1.0.so.0+0x129bf] pango_context_get_matrix+0x1f C [libgdk-x11-2.0.so.0+0x1ba1b] __float128+0xfb C [libgdk-x11-2.0.so.0+0x1be95] __float128+0x105 C [libswt-pi-gtk-3659.so+0x38c88] Java_org_eclipse_swt_internal_gtk_OS__1gdk_1draw_1layout+0x27 J org.eclipse.swt.internal.gtk.OS._gdk_draw_layout(IIIII)V J org.eclipse.swt.internal.gtk.OS.gdk_draw_layout(IIIII)V j org.eclipse.swt.widgets.Composite.gtk_expose_event(II)I+42 j org.eclipse.swt.widgets.Canvas.gtk_expose_event(II)I+49 ..............................
What GTK version are you running on your distro?
(In reply to comment #11) > What GTK version are you running on your distro? following is everything related to gtk : usermode-gtk-1.88-3.el5.2 gtk+-1.2.10-56.el5 gtk+-1.2.10-56.el5 gtk2-devel-2.10.4-21.0.1.el5_5.6 gtk2-engines-2.8.0-3.el5 gnome-python2-gtkmozembed-2.14.2-7.el5 pygtk2-libglade-2.10.1-12.el5 libgtk-java-2.8.7-3.el5 authconfig-gtk-5.3.21-6.el5 gtkhtml3-devel-3.16.3-1.el5 gtk-vnc-0.3.8-3.el5 gtkhtml2-2.11.0-3 gtkhtml2-devel-2.11.0-3 pygtk2-devel-2.10.1-12.el5 gtksourceview-devel-1.8.0-1.fc6 pygtk2-codegen-2.10.1-12.el5 gtkspell-2.0.11-2.1 pinentry-gtk-0.7.3-3.el5 gtk-doc-1.7-1.fc6 gtkspell-2.0.11-2.1 libgtk-java-devel-2.8.7-3.el5 gtkhtml3-3.16.3-1.el5 gnome-python2-gtkspell-2.14.2-7.el5 mtr-gtk-0.71-3.1 gtk+-devel-1.2.10-56.el5 gtkspell-devel-2.0.11-2.1 gtksourceview-1.8.0-1.fc6 gnome-python2-gtkhtml2-2.14.2-7.el5 gtk2-2.10.4-21.0.1.el5_5.6 scim-bridge-gtk-0.4.5-9.el5 gtkspell-devel-2.0.11-2.1 libswt3-gtk2-3.2.1-19.el5.0.1 gtksourceview-1.8.0-1.fc6 gtk-vnc-devel-0.3.8-3.el5 gtk-vnc-devel-0.3.8-3.el5 gtkhtml3-3.16.3-1.el5 gtksourceview-devel-1.8.0-1.fc6 gtk2-engines-2.8.0-3.el5 gtk+-devel-1.2.10-56.el5 pygtk2-devel-2.10.1-12.el5 gtkhtml2-devel-2.11.0-3 gtkhtml3-devel-3.16.3-1.el5 pygtk2-2.10.1-12.el5 gnome-python2-gtksourceview-2.16.0-3.el5 libgtk-java-2.8.7-3.el5 scim-bridge-gtk-0.4.5-9.el5 gtkhtml2-2.11.0-3 gtk-vnc-python-0.3.8-3.el5 gtk-vnc-0.3.8-3.el5 ghostscript-gtk-8.70-6.el5 gtk2-2.10.4-21.0.1.el5_5.6 gtk2-devel-2.10.4-21.0.1.el5_5.6 libgtk-java-devel-2.8.7-3.el5
Created attachment 219543 [details] Crash log on SuSE 11 SP2 with $DISPLAY to MacOS X Lion X Server I get the same crash running eclipse 3.0.0 M3 on SuSE Linux 11 SP2, with my $DISPLAY set to a remote MacBook Pro running OSX 10.7.4, and its usual X11.app.
I see a crash in SUSE 11 sp1 64 bit, when I open a java file in a new workspace. Eclipse 4.2.2 gtk2-2.18.9-0.4.1 pango-1.26.2-1.1.249
Has anybody seen this crash on Eclipse 4.3 (Kepler) and are there any reproducible steps? I'm not sure we can do much without being able to reproduce the crash consistently.
Resolving the bug as there has been no response. Please reopen if the crash can be reproduced either with Eclipse Kepler (4.3) or Luna (4.4) versions.
Agreed. I've switched to Ubuntu 12.04 since then, and haven't seen the crash in a very long time.
