eclipse reports memory corruption, crashes

I attached this to Firefox, too, because it owns the library. Firefox gives the same warning, though I didn't notice instability yet.

Can you please give me a step-by-step instruction on how you can crash
it? Please assume that my eclipse is completely fresh (e.g. a newly
created workspace).

Thanks,

 - Alexander

OK, so I tried creating a new workspace, with the bug "enabled" (ie, the libmozjs file in the normal position), Eclipse crashed. So I hid (renamed) the file as described above, started Eclipse again, created a workspace (it worked), stopped Eclipse, and put the file back. Then:

(1) I Started Eclipse (with the new, blank workspace),
(2) created a new Java project (named test),
(3) created a new class named Test, in package test.
(4) In the body of the class I started typing "Str" and pressed Ctrl-Space for the auto-completion.
(5) Eclipse worked the hard drive a bit, the little drop-box with the possible completions showed up, and a couple of seconds later Eclipse crashed. In quick succession:
    a. The error message appeared in the console (the one with "#" at the start of the lines);
    b. The Eclipse window disappeared;
    c. The dialog box that Eclipse shows on crashes appeared (see the contents below).

The exact same thing happens in any case when I press Ctrl+Space (and also on automatic autocomplete), in any class in any project. It does happen in other situations, too (like when I switch to a _new_ project, not one that exists already). And the error is with the same file, as far as I can tell. (Note, however, that the gslice/memory warning appears right when Eclipse starts.)

JVM terminated. Exit code=1
/usr/lib/jvm/java/bin/java
-Djava.library.path=/usr/lib/jni
-Dgnu.gcj.precompiled.db.path=/var/lib/gcj-4.1/classmap.db
-Dgnu.gcj.runtime.VMClassLoader.library_control=never
-Dosgi.locking=none
-jar /usr/lib/eclipse/startup.jar
-os linux
-ws gtk
-arch x86
-launcher /usr/lib/eclipse/eclipse
-name Eclipse
-showsplash 600
-exitdata 420013
-install /usr/lib/eclipse
-vm /usr/lib/jvm/java/bin/java
-vmargs
-Djava.library.path=/usr/lib/jni
-Dgnu.gcj.precompiled.db.path=/var/lib/gcj-4.1/classmap.db
-Dgnu.gcj.runtime.VMClassLoader.library_control=never
-Dosgi.locking=none
-jar /usr/lib/eclipse/startup.jar

I can confirm the eclipse crash with the java-1.5.0-sun and java-6-sun VMs, but not with java-gcj (although the warning appears there, too) - which seems to be the default.
The bug appears e.g. after /usr/lib/jvm/java-gcj/bin/java gets started by the eclipse wrapper script.
It seems the bug should rather get filed against the Java VM(s) and not eclipse?!

Haven't seen this happening in a long while.

The same behavior is happening to me. I can't even start eclipse. It crashes immediately. I have tried installing, re-installing and downloading the version from eclipse.org. I am running a fresh install of hardy (32 bit). This occurs with java 1.5, 1.6 and gcj. This seems to me to be a critical bug since it is preventing me from development work. I am now having to boot into windows! just to work on java! Whoever decided to release hardy with a broken java/eclipse packages should feel ashamed.

I have found a solution. I completely removed the eclipse that came from the repos. And I made sure that my default java was the sun 1.5 version. Then I downloaded the newest ganymede release candidate from eclipse.org, and it worked fine.