Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 368639

Summary: Eclipse crashes in Fedora 16
Product: [WebTools] WTP ServerTools Reporter: Harish Bayyavarapu <whimsical1987>
Component: wst.serverAssignee: wst.server <wst.server-inbox>
Status: NEW --- QA Contact: Elson Yuen <eyuen7>
Severity: normal    
Priority: P3 CC: daniel_megert, whimsical1987
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Harish Bayyavarapu CLA 2012-01-16 01:55:31 EST
Build Identifier: 20110916-0149

Method 1:
Open the eclipse from the terminal command

eclipse]$ ./eclipse
** (Eclipse:3119): DEBUG: NP_Initialize
** (Eclipse:3119): DEBUG: NP_Initialize succeeded
(npviewer.bin:3181): GnomeShellBrowserPlugin-DEBUG: plugin loaded
ERROR: Invalid browser function table. Some functionality may be restricted.
(Eclipse:3119): GnomeShellBrowserPlugin-DEBUG: plugin loaded
ERROR: Invalid browser function table. Some functionality may be restricted.
** (Eclipse:3119): DEBUG: NP_Initialize
** (Eclipse:3119): DEBUG: NP_Initialize succeeded
** (Eclipse:3119): DEBUG: NP_Initialize
** (Eclipse:3119): DEBUG: NP_Initialize succeeded
java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.4) (fedora-61.1.10.4.fc16-i386)
OpenJDK Server VM (build 20.0-b11, mixed mode)
** (Eclipse:3119): DEBUG: NP_Initialize
** (Eclipse:3119): DEBUG: NP_Initialize succeeded
** (Eclipse:3119): DEBUG: NP_Initialize
** (Eclipse:3119): DEBUG: NP_Initialize succeeded
No bp log location saved, using default.
[000:000] Browser XEmbed support present: 1
[000:000] Browser toolkit is Gtk2.
[000:001] Using Gtk2 toolkit
[000:002] No bp log location saved, using default.
[000:002] Browser XEmbed support present: 1
[000:002] Browser toolkit is Gtk2.
[000:002] Using Gtk2 toolkit
No bp log location saved, using default.
[000:023] Browser XEmbed support present: 1
[000:023] Browser toolkit is Gtk2.
[000:024] Using Gtk2 toolkit
** (Eclipse:3119): DEBUG: NP_Initialize
** (Eclipse:3119): DEBUG: NP_Initialize succeeded
** (Eclipse:3119): DEBUG: NP_Initialize
** (Eclipse:3119): DEBUG: NP_Initialize succeeded
** (Eclipse:3119): DEBUG: NP_Initialize
** (Eclipse:3119): DEBUG: NP_Initialize succeeded
Segmentation fault


Method 2:
Open eclipse from equinox launch jar

java -jar org.eclipse.equinox.launcher_1.2.0.v20110502.jar
Exception in thread "Worker-7" 
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Worker-7"
Error while logging event loop exception:
Error while logging event loop exception:
Exception in thread "Worker-1" 
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Worker-1"
Exception in thread "Worker-5" 
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Worker-5"


Reproducible: Always

Steps to Reproduce:
1.Create a sample Dynamic Web project and create a sample webservice project using Apache Axis 2
2.Write a sample sayHello service
3.Create a new Webservice and then select the wsdl file

It crashes in this eclipse. I tried running springsourcetool suite and even there it crashes. Seems like it is very unstable in Linux
Comment 1 Dani Megert CLA 2012-01-16 04:48:59 EST
Not sure I hit the right component.

At any rate, this looks like you need to give more memory when launching the server.
Comment 2 Harish Bayyavarapu CLA 2012-01-16 08:36:27 EST
I have give the min size as 256m and max as 2048m. I am assuming that should be sufficient.
Comment 3 Harish Bayyavarapu CLA 2012-01-16 08:40:12 EST
The output I have pasted earlier has java 1.6 which is an openjdk version. I am using sun jdk 1.7 currently. I have the java_home set and shouldn't the eclipse be using sun jvm instead of open jdk?
Can the crash be because of the open jdk?