[max.headroom]

my system:

suse 9.3 x86_64
sun java 1.5.0 b4
eclipse-SDK-3.1-linux-gtk-x86_64.tar.gz
EnterpriseWorkbenchInstaller_4.0M3_E3.1.bin (Xmx512m Xms256m)

eclipse alone works without a problem but with the installed myeclipse i had various crashs. with an empty new workspace everything works fine but after importing an existing projekt or even creating a new one and copy my java files into it the workbench crashed with some vm error. mostly with the following error:

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0x00002aaaaefc5e9d, pid=24007, tid=1089239392
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_04-b05 mixed mode)
# Problematic frame:
# J org.eclipse.jdt.internal.compiler.parser.Scanner.getNextToken()I
#

Please help….

[Riyad Kalla]

What is your Eclipse Build ID (Help > About)?

Also we have done no testing with the 64-bit builds of Eclipse running under a 64-bit VM, unfortunately this might be the issue. Can you trya nd download the Eclipse 3.1 SDK from elcipse.org for Linux and use that and see if it behaves?

[Scott Anderson]

One other thing that fixes many ills is restarting Eclipse with the -clean commandline option: (eclipse -clean). It causes a rebuild of the plugin cache, which has been a source of many Eclipse problems.

[max.headroom]

Eclipse Version:

Eclipse SDK
Version: 3.1.0
Build id: I20050627-1435

I’ve tried the commendline option -clean but the problem did not change.

BUT: i found a thread in the eclipse bug db and the problem seems to be a jvm (hotspot) problem. it only happens when you have installed a lot of plugins like MyEclipse do, so i first think that its a bug in your app.
Its a bug in the sun jvm 1.5.0 64 bit. See ecliopse bug id: 71987. Now i use the workaround posted by a sun employee to exclude some classes for the hotspot compiler. Azeem Jiva wrote in eclipse bugzilla:

While I’m working on this bug, there is a better workaround then just reverting
to the interpreter. Create the following file in your Eclipse directory:
.hotspot_compiler

With the contents of:

exclude org/eclipse/jdt/internal/compiler/parser/Scanner optimizedCurrentTokenSource3
exclude org/eclipse/jdt/internal/core/util/CommentRecorderScanner recordComment

This works fine and dereases preformance much less than disable the hotspot compiler general.

[max.headroom]

Now i’ve tried the new build 1.5.0_05-b05 (64 bit) of SUNs jvm. It seems to work mostly (not always) stable without the workaround above.

[chroneus]

I also have a problem installing My Eclipse on 64 bit Windows. After self extracting,launcher send message “could not load jvm.dll” or something like this. This problem appears both on java sun sdk 64 bit 1.5 and java ibm sdk 1.4 32 bit. It seems that the launcher cannot work wtih 64 bit Microsoft Windows environment. I’ve extract plugins and features using WinRar into eclipse directory and all seems work ok.

[max.headroom]

When i look at the eclipse dowload page, i found no support for 64 bit Windows. That should be the problem.

My last expirience with my problem above was, that the IBM 1.4 64 Bit JVM works well (underSuse Linux 64 Bit). I don’t have any trouble since a few weeks !!!

[arjan.tijms]

We also found out that the snapshot builds of Mustang work pretty well too. It shouldn’t be recommended really, but Sun’s 64 bit 1.5 VM proved to be so unstable that we actually tried Mustang for running Eclipse on.

One of our developpers is now running mustang/eclipse 3.1.1/MyEclipse 4.03 on Debian Linux for his daily programming, and it ‘only’ crashes about 2 or 3 times a week. This sounds bad, but its actually quite a step up from 1.5 which crashed 2 or 3 times per day.

[Author]

Posts