Bug 799069 - JVM always crashes with SIGSEGV during starting up SoapUI 4.0.1
Summary: JVM always crashes with SIGSEGV during starting up SoapUI 4.0.1
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 16
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Deepak Bhole
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-01 17:25 UTC by igarashitm
Modified: 2012-03-01 17:59 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-01 17:45:31 UTC
Type: ---
Embargoed:


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

Description igarashitm 2012-03-01 17:25:24 UTC
Created attachment 566897 [details]
hs_err_pid18461.log

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


Version-Release number of selected component (if applicable):
java-1.6.0-openjdk-1.6.0.0-65.1.11.1.fc16.x86_64

How reproducible:

Steps to Reproduce:
1.${SoapUI.install.dir}/bin/soapui.sh
2.
3.
  
Actual results:
crash with SIGSEGV

Expected results:
startup successfully

Additional info:

Comment 1 igarashitm 2012-03-01 17:38:52 UTC
Created attachment 566901 [details]
core.18461

core.18461

Comment 2 Deepak Bhole 2012-03-01 17:45:31 UTC
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 17:59:36 UTC
Hi Deepak,

Thanks for your quick reply.
I have reported it to the SoapUI forum as following:
http://www.eviware.com/forum/viewtopic.php?f=13&t=12811#p31191


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