Comments on: Eclipse just crashed so I’m going to file a bug now…

By: Ismael Juma

Ismael Juma — Fri, 11 Jul 2008 16:57:08 +0000

Just released, JDK6u10 build 27:

http://blogs.sun.com/SDNProgramNews/entry/java_se_6u10_27_is

It should include the fix.

Ismael

By: Ismael Juma

Ismael Juma — Fri, 11 Jul 2008 13:32:11 +0000

As far as I know, it’s not, but I haven’t tried. Still waiting for the JDK6u10 beta that actually includes the fix…

Ismael

By: Daniel Le Berre

Daniel Le Berre — Thu, 10 Jul 2008 13:03:36 +0000

Sun Java 6 update 7 is now available for download.

Does anyone know if the hotspot bug is corrected in this update?

I cannot figure it out on the release notes.

By: Boris Bokowski

Boris Bokowski — Wed, 02 Jul 2008 13:28:45 +0000

Martin, see bug 214092 comment 13. The JIT in IBM’s J9 VM has similar command-line options for excluding certain methods from being optimized too much, or being JITed at all (see e.g. bug 215252 comment 20).

By: Martin Oberhuber

Martin Oberhuber — Tue, 01 Jul 2008 16:26:51 +0000

Just wondering, how would one exclude classes from the scope of the Hotspot Compiler?

And just noting, one little bugzilla “trick” that I’ve been using a lot in order to see if an issue of mine has been filed already before is this:

Copy an interesting line from a backtrace related to the bug (e.g. from a .log file, or from a hs_err*.log file)
Open the bugzilla advanced search page: https://bugs.eclipse.org/bugs/query.cgi?format=advanced
Paste the line of backtrace into the “A comment:” field, select Classification: “Eclipse”, and press the Search button

You’ll find those bugzilla bugs that were filed with probably related backtraces. Just FYI, there’ve been ideas to automate that kind of search with an Eclipse “Help > Report a Bug” menu item that would automatically search bugzilla for tracebacks from your .log and automatically attach your .log when you report an issue…

By: Daniel Le Berre

Daniel Le Berre — Mon, 30 Jun 2008 16:11:01 +0000

Remi: Using a Java 5 JVM until the new JVM 6 update appears looks like a good option to me. Thanks for clarifying this.

I basically use Eclipse for two main tasks: my courses on software engineering and JEE, and SAT4J development :)

By: Remy

Remy — Mon, 30 Jun 2008 12:39:13 +0000

Daniel: Yes, the two known workarounds at the moment are to either use Java 5 or to exclude those classes. I hope that this will be the end of your Eclipse problems for the time being. Good luck with whatever you’re using Eclipse for! :)

By: Daniel Le Berre

Daniel Le Berre — Mon, 30 Jun 2008 08:25:58 +0000

The problem is the famous DeltaTreeNode problem:

From my JVM error log file:
Current CompileTask:
C2:825 org.eclipse.core.internal.dtree.DataTreeNode.forwardDeltaWith([Lorg/
eclipse/core/internal/dtree/AbstractDataTreeNode;[Lorg/eclipse/core/internal/dtr
ee/AbstractDataTreeNode;Lorg/eclipse/core/internal/dtree/IComparator;)[Lorg/eclipse/core/internal/dtree/AbstractDataTreeNode; (
469 bytes)

It looks like the fix it to exlude those classes from the scope of the Hotspot Compiler or to wait for the new update of Sun JVM.

Thanks for pointing us to the right direction!

Cheers,

Daniel

By: Remy

Remy — Sat, 28 Jun 2008 10:49:58 +0000

Daniel: Please let me know how it goes after checking your logs against the problems I have described above. If there are no matches, feel free to file a bug or try to get some help from one of Eclipse’s support avenues like the newsgroup and/or IRC.

By: Daniel Le Berre

Daniel Le Berre — Sat, 28 Jun 2008 06:19:44 +0000

I confirm that Eclipse 3.4 is currently unusable on Linux 64 (Mandriva).

I use Eclipse under the same distribution (Mandriva) on both a 32 bits and 64 bits platform.

Eclipse3.4 works like a charm on the former will it crashes after a few minutes of use on the latter (JVM bug). I cannot access that machine right now, so I cannot confirm the origin of the problem)

It is a show stopper for me because I run only 64 bits software on that machine.

Daniel