Comment 1 James Blackburn 2011-05-20 08:06:35 EDT

This is probably bug 333227 what JVM are you using?

Comment 2 alain.ruby 2011-05-20 11:02:32 EDT

(In reply to comment #1)
> This is probably bug 333227 what JVM are you using?
I am using the following :
java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8.7) (mandriva-7.b18.5mdv2010.0-x86_64)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)

Comment 3 alain.ruby 2011-05-20 11:15:10 EDT

(In reply to comment #1)
> This is probably bug 333227 what JVM are you using?
I am using the following :
java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8.7) (mandriva-7.b18.5mdv2010.0-x86_64)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)

Comment 4 alain.ruby 2011-05-20 11:16:15 EDT

Adding -XX:-UseCompressedOops to eclipse.ini doesn't seem to solve the problem

Comment 5 James Blackburn 2011-05-20 11:24:36 EDT

You need to provide more detail on the crash.  An error log + backtrace otherwise there's no way to pinpoint where the issue is.

Comment 6 alain.ruby 2011-05-20 11:42:40 EDT

Please can you tell me where the error log / backtrace are written ? because on the standrad output I get absolutly nothing...

Comment 7 James Blackburn 2011-05-20 12:55:21 EDT

There may be an hs_err_*.log in the directory in which you started eclipse (if the JVM has crashed).
In general this is known to work so this is likely an issue with your environment and not eclipse.

Comment 8 Remy Suen 2011-05-20 13:00:43 EDT

(In reply to comment #0)
> I get a systematic crash of ECLIPSE under KDE 4.3.5 (mandriva 2010, on X86_64
> intel quad core platform) when attempting to expand the lower level of
> directories, in the Project Explorer window for example.

What kind of files do you have in that folder? Is it always that one folder?

See bug 320487.

Comment 9 alain.ruby 2011-05-23 05:42:30 EDT

(In reply to comment #7)
> There may be an hs_err_*.log in the directory in which you started eclipse (if
> the JVM has crashed).
> In general this is known to work so this is likely an issue with your
> environment and not eclipse.

I get no hs_err_*.log.
You are right, it is clealy a problem between eclipse and the kde environment : when I run the same Eclipse session via an ssh session (everything in the environment is the same apart the KDE addings), I never get any crash of Eclipse.

The trouble is that Eclipse is the unique software that crashes this way with my Kde 4.3.5 session and I have no idea about what is going wrong ...

Comment 10 alain.ruby 2011-05-23 05:59:29 EDT

(In reply to comment #8)
> (In reply to comment #0)
> > I get a systematic crash of ECLIPSE under KDE 4.3.5 (mandriva 2010, on X86_64
> > intel quad core platform) when attempting to expand the lower level of
> > directories, in the Project Explorer window for example.
> What kind of files do you have in that folder? Is it always that one folder?
> See bug 320487.

Yes ! 
MALLOC_CHECK=0 eclipse seems to solve the trouble (by default it was set to 2)
Thank you for your help 

PS: by the way, setting MALLOC_CHECK=1 eclipse produces tens of error messages by glibc : 

*** glibc detected *** /usr/bin/java: free(): invalid pointer: 0x0000000003a40ed0 ***
*** glibc detected *** /usr/bin/java: free(): invalid pointer: 
0x0000000002e9f090 ***
....

Comment 11 James Blackburn 2011-05-23 06:17:42 EDT

Marking as duplicate as per comment 8 + comment 10

*** This bug has been marked as a duplicate of bug 320487 ***