| Summary: | JVM crashes at Eclipse start-up | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Pekka Enberg <penberg> |
| Component: | [OLD] Development | Assignee: | Karl Trygve Kalleberg (RETIRED) <karltk> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | major | CC: | lassahn |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 71530 | ||
|
Description
Pekka Enberg
2004-10-18 01:05:10 UTC
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. |
