3 Replies Latest reply on Sep 5, 2007 1:09 PM by cschmid

libxpcom.so SIGSEGV

lcoetzee Aug 15, 2007 8:13 AM

Hi,

firstly... congratulations. The RHDS appears to be very worthwhile.

I have one irritating thing happening, my whole eclipse crashes (the Java Runtime Environment dies).

I am running on Linux (Debian testing) with the following Java:

java version "1.6.0_02"
Java(TM) SE Runtime Environment (build 1.6.0_02-b05)
Java HotSpot(TM) Server VM (build 1.6.0_02-b05, mixed mode)

I see the following:

#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xb20e576d, pid=785, tid=3076363952
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0_02-b05 mixed mode, sharing)
# Problematic frame:
# C [libxpcom.so+0xc976d] _ZN13nsCOMPtr_baseD2Ev+0x13
#

loaded from:

/rhds/eclipse/plugins/org.jboss.tools.vpe.mozilla.gtk_2.0.0/os/linux/x86/libxpcom.so

Any ideas of why this is happening (very very often) ?

Thanks

Louis

1. Re: libxpcom.so SIGSEGV

bryanche Aug 15, 2007 9:12 AM (in response to lcoetzee)

The Visual Page Editor on Linux requires libXp. It looks like you don't have that module installed on your system. On Fedora/RHEL, you'd do something like:

yum install libXp

I'm not sure what is the equivalent for Debian.

Also, you should use JDK 1.5
Actions
2. Re: libxpcom.so SIGSEGV

lcoetzee Aug 15, 2007 10:01 AM (in response to lcoetzee)
X Printing Extension (Xprint) client library

No, I have that.

debian package is: libxp6
Actions

3. Re: libxpcom.so SIGSEGV

cschmid Sep 5, 2007 1:09 PM (in response to lcoetzee)

I have the same problem as lcoetzee.

I get a SIGSEGV fairly often and sometimes when I'm doing nothing special. I am running on SuSE 10.1 on x86. I do have a libXp.so.6 in /usr/X11R6/lib.

The error message I get is always the same:

#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xb025d76d, pid=16852, tid=3077322944
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0_02-b05 mixed mode, sharing)
# Problematic frame:
# C [libxpcom.so+0xc976d] _ZN13nsCOMPtr_baseD2Ev+0x13
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#

--------------- T H R E A D ---------------

Current thread (0x08070800): JavaThread "main" [_thread_in_native, id=16852]

siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x00ce4de0

Registers:
EAX=0x00ce4de0, EBX=0xa9f896a8, ECX=0x090c0870, EDX=0x00000000
ESP=0xbfe581a8, EBP=0xbfe581bc, ESI=0x09387778, EDI=0x09387718
EIP=0xb025d76d, CR2=0x00ce4de0, EFLAGS=0x00010292

Top of Stack: (sp=0xbfe581a8)
0xbfe581a8: b7fd7630 00000000 090c0870 b025d75a
0xbfe581b8: 090c0870 bfe581c8 a96f3063 a9f896a8
0xbfe581c8: bfe581d8 a97116c3 b0270c58 a9f896a8
0xbfe581d8: bfe581e8 a970dcd4 b0270c50 b7bc1ff4
0xbfe581e8: bfe58208 b7ad1566 00000000 00000000
0xbfe581f8: 09387710 a9f896a8 090c0870 00000000
0xbfe58208: bfe58218 a96ed7e3 a9f9fdc0 a9f896a8
0xbfe58218: bfe58228 a9dc09bc 00000000 b7fdfff4

Instructions: (pc=0xb025d76d)
0xb025d75d: 83 ec 08 8b 45 08 83 38 00 74 0e 83 ec 0c 8b 00
0xb025d76d: 8b 10 50 ff 52 08 83 c4 10 c9 c3 55 89 e5 83 ec

Stack: [0xbfe0a000,0xbfe5a000), sp=0xbfe581a8, free space=312k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libxpcom.so+0xc976d] _ZN13nsCOMPtr_baseD2Ev+0x13
C [libxul.so+0x455063] _ZN8nsCOMPtrI11nsISupportsED1Ev+0x17
C [libxul.so+0x4736c3] _ZN20nsFastLoadFileReader16nsObjectMapEntryD1Ev+0x1b
C [libxul.so+0x46fcd4]
C [libc.so.6+0x2b566] __cxa_finalize+0x86
C [libxul.so+0x44f7e3]
C [libxul.so+0xb229bc]
C [ld-linux.so.2+0x11f02]
C [libdl.so.2+0xee4]
C [ld-linux.so.2+0xd3a6]
C [libdl.so.2+0x12fc]
C [libdl.so.2+0xf1a] dlclose+0x2a
C [libswt-xpcominit-gtk-3346.so+0x2c8a]
C [libswt-xpcominit-gtk-3346.so+0x1d9d]
C [libswt-xpcominit-gtk-3346.so+0x1013] Java_org_eclipse_swt_internal_mozilla_XPCOMInit_XPCOMGlueShutdown+0xb
j org.eclipse.swt.internal.mozilla.XPCOMInit.XPCOMGlueShutdown()I+0
j org.eclipse.swt.browser.Mozilla.create(Lorg/eclipse/swt/widgets/Composite;I)V+466
j org.eclipse.swt.browser.Browser.<init>(Lorg/eclipse/swt/widgets/Composite;I)V+213
j org.eclipse.jface.internal.text.html.BrowserInformationControl.isAvailable(Lorg/eclipse/swt/widgets/Composite;)Z+12
j org.eclipse.jdt.internal.ui.text.java.AbstractJavaCompletionProposal.getInformationControlCreator()Lorg/eclipse/jface/text/IInformationControlCreator;+9
j org.eclipse.jface.text.contentassist.AdditionalInfoController.computeInformation()V+18
j org.eclipse.jface.text.AbstractInformationControlManager.doShowInformation()V+11
j org.eclipse.jface.text.AbstractInformationControlManager.showInformation()V+8
j org.eclipse.jface.text.contentassist.AdditionalInfoController.showInformation(Lorg/eclipse/jface/text/contentassist/ICompletionProposal;Ljava/lang/Object;)V+64
j org.eclipse.jface.text.contentassist.AdditionalInfoController$10.showInformation(Lorg/eclipse/jface/text/contentassist/ICompletionProposal;Ljava/lang/Object;)V+6
j org.eclipse.jface.text.contentassist.AdditionalInfoController$9.run()V+36
J org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Z)Z
J org.eclipse.swt.widgets.Display.readAndDispatch()Z
j org.eclipse.ui.internal.Workbench.runEventLoop(Lorg/eclipse/jface/window/Window$IExceptionHandler;Lorg/eclipse/swt/widgets/Display;)V+9
j org.eclipse.ui.internal.Workbench.runUI()I+336

.... clipped ...

I have played around with memory setting for Java and have especially also increased the PermGen space. Java is Sun JDK 1.6.0_02.

No Java errors (such as NullPointerException or anything else) appear on the console before the crash.

This is really annoying, especially as everything seems to be running fine until the crash. I have the VPE visual editor and it seems to be working fine. I can start the server and the automatic publishing seems to be working as well. If it were not for these ominous crashes.

It seems to be having something to do with XPCOM, which I guess is a COM channel between RHDS and the Mozilla code. Does anybody know how to fix this in the setup, or is it just a bug in the code somewhere?

Any help/pointers would be appreciated.

BTW: I also tried on JDK 1.5.0_06, exactly the same thing... If anyone wants the hs_err_pid9999.log files from the JVM, I have plenty of the lying around... ;-)

Thanks,
Claus

Go to original post