Bug 160502 - JVM crash at random intervals on SUSE 9 with Sun JRE 1.5
Summary: JVM crash at random intervals on SUSE 9 with Sun JRE 1.5
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Linux
: P3 blocker with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Bogdan Gheorghe CLA
QA Contact:
URL:
Whiteboard:
Keywords: vm
Depends on:
Blocks:
 
Reported: 2006-10-11 12:13 EDT by Clare Carty CLA
Modified: 2012-02-07 17:06 EST (History)
10 users (show)

See Also:


Attachments
screenshot of crash (131.55 KB, image/jpeg)
2006-10-11 12:14 EDT, Clare Carty CLA
no flags Details
Log file of "random" crash (54.88 KB, text/x-log)
2006-12-28 04:08 EST, Bradley Richards CLA
no flags Details
Log file of restart attempt (51.81 KB, text/x-log)
2006-12-28 04:09 EST, Bradley Richards CLA
no flags Details
Crash with MaxPermSize=256m (51.60 KB, text/x-log)
2007-01-04 03:15 EST, Bradley Richards CLA
no flags Details
Screenshot of crash using JVM 6 (258.73 KB, image/png)
2007-02-01 06:00 EST, Thomas Aleth CLA
no flags Details
various error codes. (143.67 KB, text/plain)
2007-02-08 16:04 EST, tkman CLA
no flags Details
Variosu errors and eclipse log trace as well. (206.71 KB, text/plain)
2007-02-08 16:22 EST, tkman CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Clare Carty CLA 2006-10-11 12:13:53 EDT
JVM terminations/application crash at unpredictable intervals; sometimes on eclipse startup, sometimes after import of different files, sometimes during file opening. There's no specific pattern. 

Exit code = 6
Comment 1 Clare Carty CLA 2006-10-11 12:14:47 EDT
Created attachment 51765 [details]
screenshot of crash

Screenshot is attached
Comment 2 Clare Carty CLA 2006-10-11 12:24:13 EDT
Additional information: This bug was found during testing with another product and isolated to Eclipse GA on Sun JRE where it was reproduced. We were unable to find any stack tracebacks, core dumps or other debug information, but that may have been due to how eclipse was installed.

The issue was more difficult to reproduce on eclipse than on our product - it took  some considerable fiddling around at times, importing and opening files, closing, editing and saving to provoke the crash. 
Comment 3 Pascal Rapicault CLA 2006-10-11 15:11:51 EDT
I'm sorry but we really don't have enough details to be able to track this problem. Could you try with another VM?
Comment 4 Clare Carty CLA 2006-10-11 15:28:27 EDT
(In reply to comment #3)
> I'm sorry but we really don't have enough details to be able to track this
> problem. Could you try with another VM?
> 

Problem didn't happen with another JRE - just the sun JRE.
Comment 5 Oleg Besedin CLA 2006-10-11 15:38:06 EDT
This looks like a duplicate of the bug 92250. Could you try if error occurs with  -XX:MaxPermSize=256m  ?
Comment 6 Pascal Rapicault CLA 2006-10-12 12:57:13 EDT
After further investigation, setting the permgenspace to 1024 resolved the problem.

*** This bug has been marked as a duplicate of 92250 ***
Comment 7 Clare Carty CLA 2006-10-12 15:18:19 EDT
This problem is still occurring on the dependent product with MaxPermSize set to 1024M. Please investigate.
Comment 8 John Arthorne CLA 2006-10-12 17:24:20 EDT
What version of the Sun JRE are you using?  I suggest trying with 1.5.0_07 or later, as there are known memory leak problems with 1.5.0_06 or earlier.
Comment 9 Clare Carty CLA 2006-10-13 09:17:41 EDT
(In reply to comment #8)
> What version of the Sun JRE are you using?  I suggest trying with 1.5.0_07 or
> later, as there are known memory leak problems with 1.5.0_06 or earlier.
> 

I'm using 1.5.0_08
Comment 10 Pascal Rapicault CLA 2006-10-19 16:08:54 EDT
Without additional information there is nothing more we can do. Here is the list (in order of priority) of the things we need:
 - the log of the VM crash
 - the console ouput while running with the -XX:+PrintGCDetails vm argument
 - the set of active bundles (can be obtained in the configuration details)
 - the workspace log file
Comment 11 Bradley Richards CLA 2006-12-28 04:08:56 EST
Created attachment 56218 [details]
Log file of "random" crash
Comment 12 Bradley Richards CLA 2006-12-28 04:09:35 EST
Created attachment 56219 [details]
Log file of restart attempt
Comment 13 Bradley Richards CLA 2006-12-28 04:12:35 EST
I have the the same (or at least very similar) problem. Eclipse runs fine for 30 minutes, or a few hours, or a couple of days. Then it crashes. Once crashed, any attempt to restart it fails - I am not out of memory, and can find no obvious problem. Logging out and logging back in solves the problem.

I have attached two log files. If you require any further information, I will be happy to provide it.

Cheers,

Brad
Comment 14 Bradley Richards CLA 2007-01-04 03:15:22 EST
Created attachment 56372 [details]
Crash with MaxPermSize=256m

After submitting the last logs, I have been using Eclipse with the parameters recommended in the other bug report:  -XX:MaxPermSize=256m -XX:+PrintGCDetails 

I have just experienced the first "random" crash since using these parameters. In case it is important, I am attaching here the log-file of that crash
Comment 15 Thomas Aleth CLA 2007-02-01 05:59:28 EST
I switch this week to OpenSuse 10.2:
This bug was not here on my Suse 9.1.
Using the following VM parameter : 
-vmargs -Duser.language=en -Xms512M -Xmx728M -XX:PermSize=512M -XX:MaxPermSize=1024M  -XX:+PrintGCDetails
JVM terminations/application crash at unpredictable intervals;
I install some JVM to test 
The result are : 
With SUN JVM 5 or 6  : error code is  Exit code = 6
With BEA 5 Exit code=11
With SUN 1.4.2 Exit code=1

Using GTK or motif Eclipse version

So Eclipse crashs with every JVM I try with.
I have only the log file into the .metadata without info about the crash.

Comment 16 Thomas Aleth CLA 2007-02-01 06:00:47 EST
Created attachment 57993 [details]
Screenshot of crash using JVM 6
Comment 17 Thomas Aleth CLA 2007-02-01 06:22:58 EST
The crash occurs when using Eclipse (never occurs in background)
On KDE and Window Maker (I did not try another GUI)
Where I can find the log file for the crash ?
Comment 18 tkman CLA 2007-02-08 16:04:27 EST
Created attachment 58600 [details]
various error codes.

This contains two different error displays where eclipse is using jre 1.5 and jre 1.6.
It also shows the environmental variables in the linux environment.
There is also stack dump when trying to look at the properties of a project.  This may or may not be related but is happening at the same time so i included it.
Comment 19 tkman CLA 2007-02-08 16:07:24 EST
this is readily reproducible.  It is still random but I am unable to work for longer than 5 minutes before this crashes.  It has happened when opening up help, during a debug session when changing the perspective.  It has happened when just changing the perspective without running my application code.
Comment 20 tkman CLA 2007-02-08 16:22:07 EST
Created attachment 58601 [details]
Variosu errors and eclipse log trace as well.

This is the same information as previous attachment but it also includes the eclipse log trace.
Comment 21 J.F.Lanting CLA 2007-03-29 02:22:13 EDT
I can not run ECLIPSE on JAVA 6.0 on SuSE LINUX 9.0 since ECLIPSE 3.3M4

In other words: 3.3M5, 3.3M5eh and 3.3M6 crash before any display.
Am I the only one in the world running ECLIPSE on SuSE LINUX 9.0?

;JOOP!
Comment 22 Steve Northover CLA 2007-04-01 09:32:34 EDT
Bogdan, please work with Bradley to recreate the crash.  He seems to crash in gtk_expose() although the actual GTK call that crashes is different.  Could it be a cairo issued?  Please get the Linux version details.

tkman's crash seems bogus (it's an exception, not a VM crash).  His stack trace shows this:

java.lang.InstantiationException: com.aptana.ide.editors.views.outline.propertyManager.PropertyManager
Comment 23 Steve Northover CLA 2007-04-01 09:35:15 EDT
J.F. Lanting, can you please open another bug report describing the trouble with Java 6 (add me and Bogdan to the CC)?  We should be able to browse changes between M4 and M5 to get to the bottom of it.
Comment 24 Bogdan Gheorghe CLA 2007-04-26 14:56:27 EDT
Bradley, are you still having problems with 3.3 M6? If so, could you let me know your GTK version details as well as the rest of your config details (rpm -q gtk2 cairo atk pango glib2).

JF Lanting, are you still having difficulties? I was able to run 3.3M6 on Suse9 with Sun's JRE6. If you are still having problems can you please open a new bug? Thanks!

Comment 25 Jason Zhu CLA 2007-08-05 21:59:59 EDT
I am having the similar problem with exit code =6, on Red Hat Enterprise with eclipse 3.2, and SUN jdk1.5.0_10.  I am doing an evaluation procedure to decide if our company software development should move onto Linux with Eclipse, currently we are on Window XP + VMWare.

Eclipse is OK if left to run for few days, but it crashed whenever pressing CTRL + space to prompt hints for variables or methods etc.
Comment 26 Bogdan Gheorghe CLA 2007-08-07 17:43:12 EDT
Jason - do you have a stack trace? Have you tried it with the 3.3 release? Have you tried another JRE? (Like Sun's 6_01?)
Comment 27 Jason Zhu CLA 2007-08-09 09:14:18 EDT
Thanks, Bogdan.  I will try your suggestion and get back to you the results.
Comment 28 Mike Wilson CLA 2008-06-19 14:08:10 EDT
We are not seeing this problem with current versions of Eclipse and current JVMs on SUSE9 or 10, and have gotten no new info from reporters since last August, so I'm closing this as WORKSFORME. If you are still seeing this problem, please re-open and indicate as much detail as possible about your configuration and what you were doing when the crash occurred.

Comment 29 Péter CLA 2012-02-07 17:06:06 EST
I am now also getting this very same error (definitely not WORKSFORME) with Eclipse 3.7.1 on Windows 7 64-bit.
Exit code 6!
If this helps, the problem started appearing when along with the 64-bit JRE 7, I also installed the 32-bit JRE 6 for some old software.