Bug 799069 - JVM always crashes with SIGSEGV during starting up SoapUI 4.0.1
JVM always crashes with SIGSEGV during starting up SoapUI 4.0.1
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk (Show other bugs)
x86_64 Linux
unspecified Severity urgent
: ---
: ---
Assigned To: Deepak Bhole
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-03-01 12:25 EST by igarashitm
Modified: 2012-03-01 12:59 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-03-01 12:45:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
hs_err_pid18461.log (73.78 KB, text/x-log)
2012-03-01 12:25 EST, igarashitm
no flags Details
core.18461 (46 bytes, text/plain)
2012-03-01 12:38 EST, igarashitm
no flags Details

  None (edit)
Description igarashitm 2012-03-01 12:25:24 EST
Created attachment 566897 [details]

Description of problem:
JVM always crashes with SIGSEGV during starting up SoapUI 4.0.1

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:
crash with SIGSEGV

Expected results:
startup successfully

Additional info:
Comment 1 igarashitm 2012-03-01 12:38:52 EST
Created attachment 566901 [details]

Comment 2 Deepak Bhole 2012-03-01 12:45:31 EST
Hi. Looking at the hs_err file, this error looks unrelated to the Java VM. The problem appears to be in the surrounding code that SoapUI is using. This line indicates where the error occurred:

# C  [libgconf-2.so.4+0x199d1]  gconf_enum_to_string+0xc01

Which is in gconf code and is not part of Java. The call stack shows no Java code on it either:

j  org.mozilla.xpcom.internal.GREImpl.notifyProfile()V+0
j  org.mozilla.xpcom.Mozilla.notifyProfile()V+4
j  com.teamdev.xpcom.a.a()V+691
j  com.teamdev.xpcom.b$a.run()V+13
v  ~StubRoutines::call_stub

This should be filed with the SoapUI developers upstream as there is nothing we can do about it.
Comment 3 igarashitm 2012-03-01 12:59:36 EST
Hi Deepak,

Thanks for your quick reply.
I have reported it to the SoapUI forum as following:

Note You need to log in before you can comment on or make changes to this bug.