When I start Eclipse 3.0.1, JVM dies a horrible death claiming Internal Error. I have tested with various 2.6 kernels and I can always reproduce the crash. I am running Sun JDK 1.4.2_06 but I can reproduce the crash with Blackdown 1.4.2_rc1 also. Reproducible: Always Steps to Reproduce: 1. Start Eclipse 2. File > New > Project 3. Select Java project and click Next 4. Type "foo" and click Finish 5. When asked for changing perspective, click Yes Actual Results: # # HotSpot Virtual Machine Error, Internal Error # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Client VM (1.4.2_06-b03 mixed mode) # # Error ID: 43113F32554E54494D45110E4350500308 # # Problematic Thread: prio=1 tid=0x0805bb08 nid=0x32f9 runnable # Heap at VM Abort: Heap def new generation total 576K, used 575K [0xab8b0000, 0xab950000, 0xabd90000) eden space 512K, 99% used [0xab8b0000, 0xab92ffa8, 0xab930000) from space 64K, 99% used [0xab930000, 0xab93fff8, 0xab940000) to space 64K, 0% used [0xab940000, 0xab940000, 0xab950000) tenured generation total 7168K, used 5397K [0xabd90000, 0xac490000, 0xaf8b0000) the space 7168K, 75% used [0xabd90000, 0xac2d5498, 0xac2d5600, 0xac490000) compacting perm gen total 15360K, used 15243K [0xaf8b0000, 0xb07b0000, 0xb38b0000) the space 15360K, 99% used [0xaf8b0000, 0xb0792e78, 0xb0793000, 0xb07b0000) Portage 2.0.51_rc9 (default-x86-2004.0, gcc-3.4.2, glibc-2.3.4.20041006-r0, 2.6.9-rc4 i686) ================================================================= System uname: 2.6.9-rc4 i686 Intel(R) Celeron(R) CPU 2.80GHz Gentoo Base System version 1.5.3 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2-r1 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium3 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium3 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks sandbox" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apm arts avi berkdb bitmap-fonts crypt cups encode esd f77 foomaticdb gdbm gif gnome gphoto2 gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif mpeg mysql ncurses nls nptl oggvorbis opengl oss pam pdflib perl png python qt quicktime readline ruby sdl slang spell ssl svga tcltk tcpd tetex truetype x86 xml2 xmms xprint xv zlib"
Sun JDK 1.5.0 works ok.
Workarounds: 1.4.2 works if I pass "-vmargs -Xint", "-vmargs -Dosgi.locking=none", or "-vmargs -server" to Eclipse as command line arguments.
Update to above, I can reproduce the crash with "-vmargs -server" and "-vmargs -Dosgi.locking" on 1.4.2 also. It just takes little more work to trigger the bug. To summarize: 1.4.2_06 (default) Crashes with submitted test case. 1.4.2_06 (-server) Crashes with little more beating. 1.4.2_06 (-Dosgi.locking) Crashes with little more beating. 1.4.2_06 (-Xint) Works ok. 1.5.0 (default) Works ok.
Can you reproduce this with the binary drop from eclipse.org for the same version of Eclipse that you compiled from source code?
I am not sure if the binary drop is 3.0 or 3.0.1 but I can reproduce the crash with it. I can double check the version if you want. Initially, I was testing the binary release from eclipse.org and only after hitting the bug I emerged eclipse-sdk from portage. Both crash the JVM. FWIW, a Sun engineer mentioned in a private mail that although they were unable to reproduce my problem they have fixed similar bugs in the JITter after 1.4.2. You can see some of the problems reported here [1]. That would also explain why 1.5.0 does not crash. 1. http://onesearch.sun.com/search/developers/index.jsp?charset=UTF-8&qt=%2B43113F32554E54494D45110E4350500308&col=javabugs
hi, i have the same problem. i tried eclipse-3 -Xint as well, but eclipse crashes too. this happens with the emerged version as well as with the bin version from eclipse.org. (3.0.1) this is the error message: JVM terminated. Exit code=1 /opt/blackdown-jdk-1.4.1/bin/java -cp /home/cb/tmp/eclipse/startup.jar org.eclipse.core.launcher.Main -os linux -ws gtk -arch x86 -showsplash /home/cb/tmp/eclipse/eclipse -showsplash 600 -exitdata /home/cb/tmp/eclipse/eclipse -exitdata 1d20000 -vm /opt/blackdown-jdk-1.4.1/bin/java -vmargs -cp /home/cb/tmp/eclipse/startup.jar org.eclipse.core.launcher.Main
with sun-jdk: # # HotSpot Virtual Machine Error, Internal Error # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Client VM (1.4.2_06-b03 mixed mode) # # Error ID: 43113F32554E54494D45110E4350500308 # # Problematic Thread: prio=1 tid=0x086fabe0 nid=0x6477 runnable # Heap at VM Abort: Heap def new generation total 2496K, used 2411K [0xab8c0000, 0xabb70000, 0xabda0000) eden space 2240K, 99% used [0xab8c0000, 0xabaef520, 0xabaf0000) from space 256K, 68% used [0xabb30000, 0xabb5ba80, 0xabb70000) to space 256K, 0% used [0xabaf0000, 0xabaf0000, 0xabb30000) tenured generation total 32140K, used 19281K [0xabda0000, 0xadd03000, 0xaf8c0000) the space 32140K, 59% used [0xabda0000, 0xad074770, 0xad074800, 0xadd03000) compacting perm gen total 18176K, used 17935K [0xaf8c0000, 0xb0a80000, 0xb38c0000) the space 18176K, 98% used [0xaf8c0000, 0xb0a43f00, 0xb0a44000, 0xb0a80000)
What are your CFLAGS?
Can't do much more here without more detailed info, as I can't reproduce it.
