Community
Participate
Working Groups
I'll create an attachment with the hs_err logg
Created attachment 13958 [details] Crash Information
This is clearly a bug in the VM. I don't see what we could do to fix it.
How about reporting it to java? Since it is in your class, perhaps you have better information to give them about what causes the bug than I do. org.eclipse.jdt.internal.compiler.parser.Scanner.getNextToken()I
There is nothing fancy in this method. Basically a big switch statement. I would not be surprised if this bug is already fixed in latest 1.5 drops.
Closing as INVALID. This is a VM bug.
Sun doesn't believe this is a VM bug, but I'm getting it over and over again. Please check it out: This one is with jumpOverMethodBody() # # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGSEGV (0xb) at pc=0x0000002a99f9d97a, pid=9252, tid=16384 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0-rc-b63 mixed mode) # Problematic frame: # J org.eclipse.jdt.internal.compiler.parser.Scanner.jumpOverMethodBody()V # # An error report file with more information is saved as hs_err_pid9252.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp #
The nature of the crash reveals something went wrong on VM side. Even if we were running some invalid classfile, the VM should defensively throw some exception, not issue such a crash. VM have bugs, like any other piece of software, and we likely exposed one here. May I suggest switching to a different VM vendor to see if it changes behavior ? Does it only occur on 64bits platform ? We could tweak the source code until we no longer hit the VM bug, but this would require first us to be able to reproduce it, which we haven't, and this would only be a workaround for some vendor VM bug.
I have tried the blackdown 1.4.2_rc VM and it just happened again. I have not tried another platform. I'm running AMD 64. Heres SUN's reply to the issue. They blame eclipse, you blame them. I have no idea.... The below report is for the (build 1.5.0-rc-b63, mixed mode) VM. ================================================================= Thank you for reporting this issue. Please ask Eclipse to investigate this issue further. Since the Eclipse implementation of getNextToken() appears to trigger this failure, the developers of Eclipse will be able to examine their product, isolate the cause of the behavior, and, if necessary, provide us with a detailed report. Regards, Jonathan ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NOTICE: This message, including any attachments, is for the intended recipient(s) only. If you are not the intended recipient(s), please reply to the sender, delete this message, and refrain from disclosing, copying, or distributing this message. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ----------------- Report ------------------- category : hotspot release : tiger-beta2 subcategory : runtime_system type : bug synopsis : Problematic frame in Scanner.getNextToken() description : FULL PRODUCT VERSION : java version "1.5.0-rc" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-rc-b63) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0-rc-b63, mixed mode) FULL OS VERSION : Linux mygentoo 2.6.5-gentoo #1 Fri Jun 4 19:05:43 EDT 2004 x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux A DESCRIPTION OF THE PROBLEM : Happens with Eclipse. They swear this must be a VM bug. STEPS TO FOLLOW TO REPRODUCE THE PROBLEM : Not sure. Seems random? ERROR MESSAGES/STACK TRACES THAT OCCUR : # # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGSEGV (0xb) at pc=0x0000002a9a05af1c, pid=8315, tid=16384 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0-rc-b63 mixed mode) # Problematic frame: # J org.eclipse.jdt.internal.compiler.parser.Scanner.getNextToken()I # # An error report file with more information is saved as hs_err_pid8315.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGSEGV (0xb) at pc=0x0000002a9a05af1c, pid=8315, tid=16384 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0-rc-b63 mixed mode) # Problematic frame: # J org.eclipse.jdt.internal.compiler.parser.Scanner.getNextToken()I # --------------- T H R E A D --------------- Current thread (0x0000000040116980): JavaThread "main" [_thread_in_Java, id=8315] siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x000000d64831dfd8 Registers: RAX=0x0000000000000205, RBX=0x0000007fbfff8b20, RCX=0x0000007fbfff8ac8, RDX=0x0000002adb3d2cc0 RSP=0x0000007fbfff8b60, RBP=0x0000000000000000, RSI=0x0000000040116980, RDI=0x0000000000000000 R8 =0x0000002adb3c2978, R9 =0x000000000000000a, R10=0x0000000000000000, R11=0x0000000000000000 R12=0x000000000000413b, R13=0x0000002adb3d2cc0, R14=0x0000000000000000, R15=0x0000000040116980 RIP=0x0000002a9a05af1c, EFL=0x0000000000010297, CSGSFS=0x0000000000000000, ERR=0x0000000000000007 TRAPNO=0x000000000000000e Top of Stack: (sp=0x0000007fbfff8b60) 0x0000007fbfff8b60: 0000002a00000000 00000001000001f9 0x0000007fbfff8b70: 0000002adb3d2bd8 0000002adb3cf5a0 0x0000007fbfff8b80: 0000002adb3d1ad0 000000000000005f 0x0000007fbfff8b90: 0000002adb3d2c4c 0000000040116980 0x0000007fbfff8ba0: 0000002adb3d2c73 0000002adb3d2c6c 0x0000007fbfff8bb0: 0000002adb3d2d00 000003e800000206 0x0000007fbfff8bc0: 0000002adb3d2bc8 0000000000000000 0x0000007fbfff8bd0: 0000002ae164def0 0000002a9a049450 0x0000007fbfff8be0: 000000ffbfff8c30 0000000700000001 0x0000007fbfff8bf0: 0000002adb3db5f0 0000007f00000586 0x0000007fbfff8c00: 0000000000000230 0000007fbfff8cb0 0x0000007fbfff8c10: 0000002ae1882367 0000000000000000 0x0000007fbfff8c20: 0000002adb3cf570 0000007fbfff8c40 0x0000007fbfff8c30: 0000002ae18812a0 0000002a99d0375e 0x0000007fbfff8c40: 0000007fbfff8cb0 0000000000000000 0x0000007fbfff8c50: 0000007fbfff8cb0 0000007fbfff8c68 0x0000007fbfff8c60: 0000002adb3cf570 0000002a99c92efe 0x0000007fbfff8c70: 0000002adb3cf570 0000007fbfff8c78 0x0000007fbfff8c80: 0000002ae1882367 0000007fbfff8d00 0x0000007fbfff8c90: 0000002ae19f6920 0000000000000000 0x0000007fbfff8ca0: 0000002ae1882420 0000007fbfff8ce0 0x0000007fbfff8cb0: 0000007fbfff8d40 0000002a99c92de1 0x0000007fbfff8cc0: 0000000000000000 0000000000000000 0x0000007fbfff8cd0: 0000002adb3c2978 0000000000000000 0x0000007fbfff8ce0: 00000000ffffffff 00000000ffffffff 0x0000007fbfff8cf0: 0000002adb3db480 0000002adb3db3f8 0x0000007fbfff8d00: 0000002adb3cf570 0000007fbfff8d08 0x0000007fbfff8d10: 0000002ae18821d5 0000007fbfff8d60 0x0000007fbfff8d20: 0000002ae19f6920 0000000000000000 0x0000007fbfff8d30: 0000002ae1882208 0000007fbfff8d50 0x0000007fbfff8d40: 0000007fbfff8da0 0000002a99c92de1 0x0000007fbfff8d50: 0000002adb3db480 0000002adb3db3f8 Instructions: (pc=0x0000002a9a05af1c) 0x0000002a9a05af0c: 45 8b 55 10 45 3b f2 0f 83 14 1c 00 00 4d 63 d6 0x0000002a9a05af1c: 41 f7 5c 95 18 eb 19 48 8b 4c 24 60 ba e9 03 00 Stack: [0x0000007fbfe00000,0x0000007fc0000000), sp=0x0000007fbfff8b60, free space=2018k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) J org.eclipse.jdt.internal.compiler.parser.Scanner.getNextToken()I [error occurred during error reporting, step 120, id 0xb] --------------- P R O C E S S --------------- Java Threads: ( => current thread ) 0x0000000040cce5b0 JavaThread "org.eclipse.jdt.internal.ui.text.JavaReconciler" daemon [_thread_blocked, id=8401] 0x0000000040f355e0 JavaThread "Worker-2" [_thread_blocked, id=8357] 0x00000000408b94a0 JavaThread "Worker-1" [_thread_blocked, id=8355] 0x0000000040f0ddb0 JavaThread "Java indexing" daemon [_thread_blocked, id=8333] 0x000000004093fc70 JavaThread "Reference Cleaner - 2" [_thread_blocked, id=8332] 0x0000000040943b50 JavaThread "Reference Cleaner - 1" [_thread_blocked, id=8331] 0x00000000407e99d0 JavaThread "Worker-0" [_thread_blocked, id=8330] 0x00000000404bd930 JavaThread "Start Level Event Dispatcher" daemon [_thread_blocked, id=8329] 0x00000000405b7f20 JavaThread "Framework Event Dispatcher" daemon [_thread_blocked, id=8328] 0x00000000401ce070 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=8324] 0x00000000401cbe00 JavaThread "CompilerThread1" daemon [_thread_blocked, id=8323] 0x00000000401ca230 JavaThread "CompilerThread0" daemon [_thread_blocked, id=8322] 0x00000000401c84d0 JavaThread "AdapterThread" daemon [_thread_blocked, id=8321] 0x00000000401c6880 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=8320] 0x00000000401b3040 JavaThread "Finalizer" daemon [_thread_blocked, id=8319] 0x00000000401b20c0 JavaThread "Reference Handler" daemon [_thread_blocked, id=8318] =>0x0000000040116980 JavaThread "main" [_thread_in_Java, id=8315] Other Threads: 0x00000000401ab060 VMThread [id=8317] 0x00000000401d0310 WatcherThread [id=8325] VM state:not at safepoint (normal execution) VM Mutex/Monitor currently owned by a thread: None Heap def new generation total 25856K, used 9835K [0x0000002adac90000, 0x0000002adc890000, 0x0000002adc890000) eden space 23040K, 33% used [0x0000002adac90000, 0x0000002adb4101d8, 0x0000002adc310000) from space 2816K, 76% used [0x0000002adc310000, 0x0000002adc52ad90, 0x0000002adc5d0000) to space 2816K, 0% used [0x0000002adc5d0000, 0x0000002adc5d0000, 0x0000002adc890000) tenured generation total 57344K, used 30157K [0x0000002adc890000, 0x0000002ae0090000, 0x0000002ae0090000) the space 57344K, 52% used [0x0000002adc890000, 0x0000002ade603410, 0x0000002ade603600, 0x0000002ae0090000) compacting perm gen total 41408K, used 41298K [0x0000002ae0090000, 0x0000002ae2900000, 0x0000002ae5290000) the space 41408K, 99% used [0x0000002ae0090000, 0x0000002ae28e48b0, 0x0000002ae28e4a00, 0x0000002ae2900000) No shared spaces configured. Dynamic libraries: 40000000-4000d000 r-xp 00000000 21:01 8306755 /home/martin/Applications/Java/jdk1.5.0/bin/java 4010c000-40110000 rw-p 0000c000 21:01 8306755 /home/martin/Applications/Java/jdk1.5.0/bin/java 40110000-4321f000 rwxp 00000000 00:00 0 2a95556000-2a9556b000 r-xp 00000000 03:03 1294730 /lib/ld-2.3.4.so 2a9556b000-2a9556c000 rw-p 00000000 00:00 0 2a9566b000-2a9566c000 rw-p 00015000 03:03 1294730 /lib/ld-2.3.4.so 2a9566c000-2a9576c000 r-xp 00000000 03:03 1337371 /lib/libpthread-0.10.so 2a9576c000-2a9576d000 r--p 00100000 03:03 1337371 /lib/libpthread-0.10.so 2a9576d000-2a9576e000 rw-p 00101000 03:03 1337371 /lib/libpthread-0.10.so 2a9576e000-2a957f2000 rw-p 00000000 00:00 0 2a957f2000-2a958f2000 r-xp 00000000 03:03 1294766 /lib/libdl-2.3.4.so 2a958f2000-2a958f4000 rw-p 00100000 03:03 1294766 /lib/libdl-2.3.4.so 2a958f4000-2a958f5000 rw-p 00000000 00:00 0 2a958f5000-2a95af5000 r-xp 00000000 03:03 1294764 /lib/libc-2.3.4.so 2a95af5000-2a95af8000 r--p 00200000 03:03 1294764 /lib/libc-2.3.4.so 2a95af8000-2a95afb000 rw-p 00203000 03:03 1294764 /lib/libc-2.3.4.so 2a95afb000-2a95b00000 rw-p 00000000 00:00 0 2a95b00000-2a96200000 r-xp 00000000 21:01 8372234 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/server/libjvm.so 2a96200000-2a963b6000 rw-p 00600000 21:01 8372234 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/server/libjvm.so 2a963b6000-2a963e4000 rw-p 00000000 00:00 0 2a963e4000-2a963e5000 r--p 00000000 00:00 0 2a9640a000-2a9650a000 r-xp 00000000 03:03 1294740 /lib/libm-2.3.4.so 2a9650a000-2a9650c000 rw-p 00100000 03:03 1294740 /lib/libm-2.3.4.so 2a9650c000-2a9660c000 r-xp 00000000 21:01 8372229 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/native_threads/libhpi.so 2a9660c000-2a96618000 rw-p 00000000 21:01 8372229 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/native_threads/libhpi.so 2a96618000-2a96620000 rw-s 00000000 03:03 2408927 /tmp/hsperfdata_martin/8315 2a9663e000-2a9673e000 r-xp 00000000 03:03 1294777 /lib/libnsl-2.3.4.so 2a9673e000-2a96740000 rw-p 00100000 03:03 1294777 /lib/libnsl-2.3.4.so 2a96740000-2a96742000 rw-p 00000000 00:00 0 2a96742000-2a96842000 r-xp 00000000 03:03 1294779 /lib/libnss_compat-2.3.4.so 2a96842000-2a96844000 rw-p 00100000 03:03 1294779 /lib/libnss_compat-2.3.4.so 2a96844000-2a96944000 r-xp 00000000 03:03 1294778 /lib/libnss_nis-2.3.4.so 2a96944000-2a96946000 rw-p 00100000 03:03 1294778 /lib/libnss_nis-2.3.4.so 2a96946000-2a96a46000 r-xp 00000000 03:03 1294772 /lib/libnss_files-2.3.4.so 2a96a46000-2a96a48000 rw-p 00100000 03:03 1294772 /lib/libnss_files-2.3.4.so 2a96a48000-2a96b48000 r-xp 00000000 21:01 8307248 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/libverify.so 2a96b48000-2a96b57000 rw-p 00000000 21:01 8307248 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/libverify.so 2a96b57000-2a96c57000 r-xp 00000000 21:01 8307261 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/libjava.so 2a96c57000-2a96c81000 rw-p 00000000 21:01 8307261 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/libjava.so 2a96c81000-2a96d81000 r-xp 00000000 21:01 8307254 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/libzip.so 2a96d81000-2a96d9c000 rw-p 00000000 21:01 8307254 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/libzip.so 2a96d9c000-2a99353000 r--s 00000000 21:01 8307315 /home/martin/Applications/Java/jdk1.5.0/jre/lib/rt.jar 2a99353000-2a993bb000 rw-p 00000000 00:00 0 2a993bb000-2a99441000 r--s 00000000 21:01 8307277 /home/martin/Applications/Java/jdk1.5.0/jre/lib/jsse.jar 2a99441000-2a99455000 r--s 00000000 21:01 8307303 /home/martin/Applications/Java/jdk1.5.0/jre/lib/jce.jar 2a99455000-2a99c90000 r--s 00000000 21:01 8307283 /home/martin/Applications/Java/jdk1.5.0/jre/lib/charsets.jar 2a99c90000-2a9a0b0000 rwxp 00000000 00:00 0 2a9a0b0000-2ad9c90000 rwxp 00420000 00:00 0 2ad9c90000-2ad9ca1000 rwxp 00000000 00:00 0 2ad9ca1000-2adac90000 rwxp 40011000 00:00 0 2adac90000-2ae2900000 rwxp 00000000 00:00 0 2ae2900000-2ae5290000 rwxp 48c70000 00:00 0 2ae5290000-2ae52cf000 rwxp 00000000 00:00 0 2ae52cf000-2ae52e3000 rwxp 4b63f000 00:00 0 2ae52e3000-2ae5316000 rwxp 00000000 00:00 0 2ae5316000-2ae532b000 rwxp 00032000 00:00 0 2ae532b000-2ae5353000 rw-p 00000000 00:00 0 2ae5353000-2ae5354000 ---p 00000000 00:00 0 2ae5354000-2ae5454000 rwxp 00001000 00:00 0 2ae5454000-2ae5457000 ---p 00101000 00:00 0 2ae5457000-2ae5554000 rwxp 00104000 00:00 0 2ae5554000-2ae5557000 ---p 00201000 00:00 0 2ae5557000-2ae5654000 rwxp 00204000 00:00 0 2ae5654000-2ae5657000 ---p 00301000 00:00 0 2ae5657000-2ae5754000 rwxp 00304000 00:00 0 2ae5754000-2ae5758000 ---p 00401000 00:00 0 2ae5758000-2ae5855000 rwxp 00402000 00:00 0 2ae5855000-2ae5859000 ---p 004ff000 00:00 0 2ae5859000-2ae5956000 rwxp 00500000 00:00 0 2ae5956000-2ae595a000 ---p 005fd000 00:00 0 2ae595a000-2ae5a57000 rwxp 005fe000 00:00 0 2ae5a57000-2ae5a5a000 ---p 006fb000 00:00 0 2ae5a5a000-2ae5b57000 rwxp 006fe000 00:00 0 2ae5b57000-2ae5b58000 ---p 007fb000 00:00 0 2ae5b58000-2ae5c58000 rwxp 007fc000 00:00 0 2ae5c58000-2ae5c5a000 r--s 00000000 21:01 8307230 /home/martin/Applications/Java/jdk1.5.0/jre/lib/ext/dnsns.jar 2ae5c5a000-2ae5c80000 r--s 00000000 21:01 8307232 /home/martin/Applications/Java/jdk1.5.0/jre/lib/ext/sunjce_provider.jar 2ae5c80000-2ae5d44000 r--s 00000000 21:01 8307289 /home/martin/Applications/Java/jdk1.5.0/jre/lib/ext/localedata.jar 2ae5d44000-2ae5d49000 r--s 00000000 21:01 8964369 /home/martin/Applications/eclipse/eclipse/startup.jar 2ae5d49000-2ae5d4c000 ---p 00000000 00:00 0 2ae5d4c000-2ae5e49000 rwxp 00003000 00:00 0 2ae5e49000-2ae5e81000 r--s 00000000 21:01 8962484 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.osgi_3.0.0/core.jar 2ae5e81000-2ae5e89000 r--s 00000000 21:01 8962485 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.osgi_3.0.0/console.jar 2ae5e89000-2ae5e95000 r--s 00000000 21:01 8962483 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.osgi_3.0.0/osgi.jar 2ae5e95000-2ae5eab000 r--s 00000000 21:01 8962487 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.osgi_3.0.0/resolver.jar 2ae5eab000-2ae5ec1000 r--s 00000000 21:01 8962488 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.osgi_3.0.0/defaultAdaptor.jar 2ae5ec1000-2ae5ee0000 r--s 00000000 21:01 8962486 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.osgi_3.0.0/eclipseAdaptor.jar 2ae5ee0000-2ae5ee3000 ---p 00000000 00:00 0 2ae5ee3000-2ae5fe0000 rwxp 00003000 00:00 0 2ae5fe0000-2ae5fe3000 ---p 00100000 00:00 0 2ae5fe3000-2ae60e0000 rwxp 00103000 00:00 0 2ae60e0000-2ae6137000 r--s 00000000 21:01 8962646 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.core.runtime_3.0.0/runtime.jar 2ae6137000-2ae6237000 r-xp 00000000 21:01 8307244 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/libnet.so 2ae6237000-2ae624e000 rw-p 00000000 21:01 8307244 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/libnet.so 2ae624e000-2ae634e000 r-xp 00000000 21:01 8307245 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/libnio.so 2ae634e000-2ae6356000 rw-p 00000000 21:01 8307245 /home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/libnio.so 2ae6356000-2ae636b000 r--s 00000000 21:01 8963173 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.core.runtime.compatibility_3.0.0/compatibility.jar 2ae636b000-2ae637f000 r--s 00000000 21:01 8979810 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.update.configurator_3.0.0/configurator.jar 2ae637f000-2ae64cd000 r--s 00000000 21:01 8963617 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.ui.ide_3.0.0/ide.jar 2ae64cd000-2ae64ce000 r--s 00000000 21:01 8979806 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.ui.workbench.compatibility_3.0.0/compatibility.jar 2ae64ce000-2ae6701000 r--s 00000000 21:01 8963168 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.ui.workbench_3.0.0/workbench.jar 2ae6701000-2ae677f000 r--s 00000000 21:01 8964024 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.jface_3.0.0/jface.jar 2ae677f000-2ae678c000 r--s 00000000 21:01 8962463 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.swt.gtk64_3.0.0/ws/gtk/swt-pi.jar 2ae678c000-2ae686b000 r--s 00000000 21:01 8962465 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.swt.gtk64_3.0.0/ws/gtk/swt.jar 2ae686b000-2ae686c000 r--s 00000000 21:01 8978931 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.ui_3.0.0/ui.jar 2ae686c000-2ae696c000 r-xp 00000000 21:01 8962477 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.swt.gtk64_3.0.0/os/linux/amd64/libswt-pi-gtk-3062.so 2ae696c000-2ae69b4000 rw-p 00000000 21:01 8962477 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.swt.gtk64_3.0.0/os/linux/amd64/libswt-pi-gtk-3062.so 2ae69b4000-2ae69b5000 rw-p 00000000 00:00 0 2ae69b5000-2ae69c3000 r--s 00000000 21:01 8978861 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.ui.console_3.0.0/console.jar 2ae69c6000-2ae69d6000 r--p 00000000 03:03 4457411 /usr/share/fonts/TTF/VeraBI.ttf 2ae69db000-2ae6cdb000 r-xp 00000000 03:03 2752799 /usr/lib/libgtk-x11-2.0.so.0.400.4 2ae6cdb000-2ae6dc7000 rw-p 00200000 03:03 2752799 /usr/lib/libgtk-x11-2.0.so.0.400.4 2ae6dc7000-2ae6dca000 rw-p 00000000 00:00 0 2ae6dca000-2ae6eca000 r-xp 00000000 03:03 2752794 /usr/lib/libgdk-x11-2.0.so.0.400.4 2ae6eca000-2ae6f49000 rw-p 00000000 03:03 2752794 /usr/lib/libgdk-x11-2.0.so.0.400.4 2ae6f49000-2ae7049000 r-xp 00000000 03:03 1441941 /usr/lib/libatk-1.0.so.0.600.1 2ae7049000-2ae7068000 rw-p 00000000 03:03 1441941 /usr/lib/libatk-1.0.so.0.600.1 2ae7068000-2ae7168000 r-xp 00000000 03:03 2758932 /usr/lib/libgdk_pixbuf-2.0.so.0.400.4 2ae7168000-2ae717d000 rw-p 00000000 03:03 2758932 /usr/lib/libgdk_pixbuf-2.0.so.0.400.4 2ae717d000-2ae727d000 r-xp 00000000 03:03 2755246 /usr/lib/libpangoxft-1.0.so.0.400.1 2ae727d000-2ae7282000 rw-p 00000000 03:03 2755246 /usr/lib/libpangoxft-1.0.so.0.400.1 2ae7282000-2ae7382000 r-xp 00000000 03:03 2753481 /usr/lib/libpangox-1.0.so.0.400.1 2ae7382000-2ae738e000 rw-p 00000000 03:03 2753481 /usr/lib/libpangox-1.0.so.0.400.1 2ae738e000-2ae748e000 r-xp 00000000 03:03 2755256 /usr/lib/libpango-1.0.so.0.400.1 2ae748e000-2ae74cc000 rw-p 00000000 03:03 2755256 /usr/lib/libpango-1.0.so.0.400.1 2ae74cc000-2ae75cc000 r-xp 00000000 03:03 2726236 /usr/lib/libgobject-2.0.so.0.400.4 2ae75cc000-2ae7607000 rw-p 00000000 03:03 2726236 /usr/lib/libgobject-2.0.so.0.400.4 2ae7607000-2ae7608000 rw-p 00000000 00:00 0 2ae7608000-2ae7708000 r-xp 00000000 03:03 2726443 /usr/lib/libgmodule-2.0.so.0.400.4 2ae7708000-2ae770b000 rw-p 00000000 03:03 2726443 /usr/lib/libgmodule-2.0.so.0.400.4 2ae770b000-2ae780b000 r-xp 00000000 03:03 2726447 /usr/lib/libgthread-2.0.so.0.400.4 2ae780b000-2ae780f000 rw-p 00000000 03:03 2726447 /usr/lib/libgthread-2.0.so.0.400.4 2ae780f000-2ae790f000 r-xp 00000000 03:03 2726684 /usr/lib/libglib-2.0.so.0.400.4 2ae790f000-2ae7993000 rw-p 00000000 03:03 2726684 /usr/lib/libglib-2.0.so.0.400.4 2ae7993000-2ae7a93000 r-xp 00000000 03:03 3164765 /usr/X11R6/lib/libXtst.so.6.1 2ae7a93000-2ae7a99000 rw-p 00000000 03:03 3164765 /usr/X11R6/lib/libXtst.so.6.1 2ae7a99000-2ae7b99000 r-xp 00000000 03:03 3164757 /usr/X11R6/lib/libX11.so.6.2 2ae7b99000-2ae7c76000 rw-p 00000000 03:03 3164757 /usr/X11R6/lib/libX11.so.6.2 2ae7c76000-2ae7d76000 r-xp 00000000 03:03 3164797 /usr/X11R6/lib/libXrandr.so.2.0 2ae7d76000-2ae7d79000 rw-p 00000000 03:03 3164797 /usr/X11R6/lib/libXrandr.so.2.0 2ae7d79000-2ae7e79000 r-xp 00000000 03:03 3165384 /usr/X11R6/lib/libXi.so.6.0 2ae7e79000-2ae7e81000 rw-p 00000000 03:03 3165384 /usr/X11R6/lib/libXi.so.6.0 2ae7e81000-2ae7f81000 r-xp 00000000 03:03 3164807 /usr/X11R6/lib/libXinerama.so.1.0 2ae7f81000-2ae7f83000 rw-p 00000000 03:03 3164807 /usr/X11R6/lib/libXinerama.so.1.0 2ae7f83000-2ae8083000 r-xp 00000000 03:03 3165494 /usr/X11R6/lib/libXext.so.6.4 2ae8083000-2ae8094000 rw-p 00000000 03:03 3165494 /usr/X11R6/lib/libXext.so.6.4 2ae8094000-2ae8194000 r-xp 00000000 03:03 3165380 /usr/X11R6/lib/libXft.so.2.1.2 2ae8194000-2ae81a8000 rw-p 00000000 03:03 3165380 /usr/X11R6/lib/libXft.so.2.1.2 2ae81a8000-2ae82a8000 r-xp 00000000 03:03 3670560 /usr/lib/libfreetype.so.6.3.4 2ae82a8000-2ae8331000 rw-p 00000000 03:03 3670560 /usr/lib/libfreetype.so.6.3.4 2ae8331000-2ae8431000 r-xp 00000000 03:03 3509745 /usr/lib/libfontconfig.so.1.0.4 2ae8431000-2ae8462000 rw-p 00000000 03:03 3509745 /usr/lib/libfontconfig.so.1.0.4 2ae8462000-2ae8464000 rw-p 00000000 00:00 0 2ae8464000-2ae8564000 r-xp 00000000 03:03 3164804 /usr/X11R6/lib/libXcursor.so.1.0.2 2ae8564000-2ae856e000 rw-p 00000000 03:03 3164804 /usr/X11R6/lib/libXcursor.so.1.0.2 2ae856e000-2ae866e000 r-xp 00000000 03:03 3165486 /usr/X11R6/lib/libXrender.so.1.2.2 2ae866e000-2ae8677000 rw-p 00000000 03:03 3165486 /usr/X11R6/lib/libXrender.so.1.2.2 2ae8677000-2ae8777000 r-xp 00000000 03:03 2753485 /usr/lib/libpangoft2-1.0.so.0.400.1 2ae8777000-2ae879f000 rw-p 00000000 03:03 2753485 /usr/lib/libpangoft2-1.0.so.0.400.1 2ae879f000-2ae889f000 r-xp 00000000 03:03 1426905 /usr/lib/libexpat.so.0.5.0 2ae889f000-2ae88c1000 rw-p 00000000 03:03 1426905 /usr/lib/libexpat.so.0.5.0 2ae88c1000-2ae89c1000 r-xp 00000000 03:03 1183743 /lib/libz.so.1.2.1 2ae89c1000-2ae89d4000 rw-p 00000000 03:03 1183743 /lib/libz.so.1.2.1 2ae89d4000-2ae8ad4000 r-xp 00000000 03:03 3460785 /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2 2ae8ad4000-2ae8ad7000 rw-p 00000000 03:03 3460785 /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2 2ae8ad7000-2ae8add000 r--s 00000000 03:03 1294784 /usr/lib/gconv/gconv-modules.cache 2ae8add000-2ae8bdd000 r-xp 00000000 03:03 1578412 /usr/lib/gconv/ISO8859-1.so 2ae8bdd000-2ae8bdf000 rw-p 00100000 03:03 1578412 /usr/lib/gconv/ISO8859-1.so 2ae8bdf000-2ae8cdf000 r-xp 00000000 21:01 8962475 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.swt.gtk64_3.0.0/os/linux/amd64/libswt-gtk-3062.so 2ae8cdf000-2ae8d22000 rw-p 00000000 21:01 8962475 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.swt.gtk64_3.0.0/os/linux/amd64/libswt-gtk-3062.so 2ae8d22000-2ae8d82000 rw-s 00000000 00:06 229381 /SYSV00000000 (deleted) 2ae8d82000-2ae8e20000 r--s 00000000 21:01 8978578 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.core.resources_3.0.0/resources.jar 2ae8e20000-2ae8e23000 ---p 00000000 00:00 0 2ae8e23000-2ae8f20000 rwxp 00003000 00:00 0 2ae8f20000-2ae8f30000 r--s 00000000 21:01 8963925 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.help_3.0.0/help.jar 2ae8f30000-2ae8f33000 ---p 00000000 00:00 0 2ae8f33000-2ae9030000 rwxp 00003000 00:00 0 2ae9030000-2ae9033000 ---p 00100000 00:00 0 2ae9033000-2ae9130000 rwxp 00103000 00:00 0 2ae9130000-2ae9230000 r-xp 00000000 03:03 3363517 /usr/lib/pango/1.4.0/modules/pango-basic-fc.so 2ae9230000-2ae9232000 rw-p 00000000 03:03 3363517 /usr/lib/pango/1.4.0/modules/pango-basic-fc.so 2ae9232000-2ae923f000 r--s 00000000 21:01 8963611 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.core.expressions_3.0.0/expressions.jar 2ae9243000-2ae9343000 r-xp 00000000 21:01 8962474 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.swt.gtk64_3.0.0/os/linux/amd64/libswt-atk-gtk-3062.so 2ae9343000-2ae934d000 rw-p 00000000 21:01 8962474 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.swt.gtk64_3.0.0/os/linux/amd64/libswt-atk-gtk-3062.so 2ae934d000-2ae9863000 r--s 00000000 21:01 8962834 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.jdt.ui_3.0.0/jdt.jar 2ae9863000-2ae98a1000 r--s 00000000 21:01 8979638 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.ui.editors_3.0.0/editors.jar 2ae98a1000-2ae98cb000 r--s 00000000 21:01 8979189 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.text_3.0.0/text.jar 2ae98cb000-2ae9962000 r--s 00000000 21:01 8963956 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.jface.text_3.0.0/jfacetext.jar 2ae9962000-2ae99bf000 r--s 00000000 21:01 8979714 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.ui.workbench.texteditor_3.0.0/texteditor.jar 2ae99bf000-2ae99cb000 r--s 00000000 21:01 8963157 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.core.filebuffers_3.0.0/filebuffers.jar 2ae99cb000-2ae99f7000 r--s 00000000 21:01 8979708 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.team.core_3.0.0/team.jar 2ae99f7000-2ae9a05000 r--s 00000000 21:01 8963188 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.ui.views_3.0.0/views.jar 2ae9a05000-2ae9a12000 r--p 00000000 03:03 4457417 /usr/share/fonts/TTF/VeraMono.ttf 2ae9a12000-2ae9a20000 r--p 00000000 03:03 4457414 /usr/share/fonts/TTF/VeraMoBI.ttf 2ae9a20000-2ae9a31000 r--p 00000000 03:03 4457410 /usr/share/fonts/TTF/Vera.ttf 2ae9a34000-2ae9b34000 r-xp 00000000 03:03 3364162 /usr/lib/pango/1.4.0/modules/pango-arabic-fc.so 2ae9b34000-2ae9b37000 rw-p 00000000 03:03 3364162 /usr/lib/pango/1.4.0/modules/pango-arabic-fc.so 2ae9b37000-2ae9c37000 r-xp 00000000 03:03 3364035 /usr/lib/pango/1.4.0/modules/pango-hangul-fc.so 2ae9c37000-2ae9c3a000 rw-p 00000000 03:03 3364035 /usr/lib/pango/1.4.0/modules/pango-hangul-fc.so 2ae9c3a000-2ae9c91000 rw-p 00000000 00:00 0 2ae9c91000-2ae9c97000 r--s 00000000 21:01 8962451 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.update.scheduler_3.0.0/scheduler.jar 2ae9c9c000-2ae9cc3000 rw-p 00032000 00:00 0 2ae9cc3000-2ae9d23000 r--s 00000000 21:01 8978803 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.search_3.0.0/search.jar 2ae9d23000-2ae9d43000 r--s 00000000 21:01 8963794 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.ltk.ui.refactoring_3.0.0/refui.jar 2ae9d43000-2ae9d4f000 r--p 00000000 03:03 4457415 /usr/share/fonts/TTF/VeraMoBd.ttf 2ae9d4f000-2ae9d69000 r--s 00000000 21:01 8963735 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.ui.externaltools_3.0.0/externaltools.jar 2ae9d91000-2ae9de8000 rw-p 00071000 00:00 0 2ae9df5000-2ae9e25000 r--p 00000000 03:03 4343554 /usr/share/fonts/misc/cu12.pcf.gz 2ae9e25000-2ae9e57000 rw-p 00000000 00:00 0 2ae9e57000-2ae9eb8000 r--s 00000000 21:01 8963962 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.compare_3.0.0/compare.jar 2ae9eed000-2ae9f05000 r--s 00000000 21:01 8979801 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.ltk.core.refactoring_3.0.0/refcore.jar 2ae9f05000-2ae9f32000 r--s 00000000 21:01 8978855 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.jdt.launching_3.0.0/launching.jar 2ae9f32000-2ae9f92000 rw-s 00000000 00:06 262150 /SYSV00000000 (deleted) 2ae9fb0000-2aea02f000 rw-p 00346000 00:00 0 2aea02f000-2aea07a000 r--s 00000000 21:01 8978586 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.update.ui_3.0.0/updateui.jar 2aea0a5000-2aea0dd000 r--s 00000000 21:01 8978572 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.debug.core_3.0.0/dtcore.jar 2aea13b000-2aea15d000 rw-p 00101000 00:00 0 2aea15d000-2aea160000 ---p 00000000 00:00 0 2aea160000-2aea25d000 rwxp 00003000 00:00 0 2aea2a9000-2aea576000 r--s 00000000 21:01 8963755 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.jdt.core_3.0.0/jdtcore.jar 2aea676000-2aea756000 r--s 00000000 21:01 8962496 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.debug.ui_3.0.0/dtui.jar 2aea756000-2aea759000 ---p 00000000 00:00 0 2aea759000-2aea856000 rwxp 00003000 00:00 0 2aea856000-2aea8c8000 r--s 00000000 21:01 8979406 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.update.core_3.0.0/updatecore.jar 2aea900000-2aea9fa000 rw-p 00038000 00:00 0 2aea9fa000-2aeaa00000 ---p ffffffffffdc7000 00:00 0 2aeaa00000-2aeaa03000 ---p 00000000 00:00 0 2aeaa03000-2aeab00000 rwxp 00003000 00:00 0 2aeab00000-2aeac00000 r-xp 00000000 03:03 1294770 /lib/libnss_dns-2.3.4.so 2aeac00000-2aeac02000 rw-p 00100000 03:03 1294770 /lib/libnss_dns-2.3.4.so 2aeac02000-2aead02000 r-xp 00000000 03:03 1294769 /lib/libresolv-2.3.4.so 2aead02000-2aead04000 rw-p 00100000 03:03 1294769 /lib/libresolv-2.3.4.so 2aead04000-2aead06000 rw-p 00000000 00:00 0 2aead06000-2aeade8000 r--s 00000000 21:01 8962681 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.jdt.debug.ui_3.0.0/jdiui.jar 2aeade8000-2aeadf4000 r--s 00000000 21:01 8963729 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.jdt.debug_3.0.0/jdi.jar 2aeadf4000-2aeae9f000 r--s 00000000 21:01 8963728 /home/martin/Applications/eclipse/eclipse/plugins/org.eclipse.jdt.debug_3.0.0/jdimodel.jar 2aeaf00000-2aeb1a8000 rw-p 00061000 00:00 0 2aeb1a8000-2aeb200000 ---p fffffffffffb4000 00:00 0 2aeb600000-2aeb7f9000 rw-p 000e4000 00:00 0 2aeb7f9000-2aeb800000 ---p 00000000 00:00 0 2aeb800000-2aebafb000 rw-p 00007000 00:00 0 2aebafb000-2aebb00000 ---p fffffffffff59000 00:00 0 2aeca00000-2aecaef000 rw-p 000c8000 00:00 0 2aecaef000-2aecb00000 ---p 000f1000 00:00 0 2aecc00000-2aeccf9000 rw-p 000df000 00:00 0 2aeccf9000-2aecd00000 ---p 00112000 00:00 0 2aece00000-2aeceff000 rw-p 00098000 00:00 0 2aeceff000-2aecf00000 ---p 000c1000 00:00 0 2aed000000-2aed0f9000 rw-p 00054000 00:00 0 2aed0f9000-2aed100000 ---p 0007f000 00:00 0 2aed200000-2aed300000 rw-p 000df000 00:00 0 7fbfe00000-7fbfe03000 ---p 00000000 00:00 0 7fbfe03000-7fc0000000 rwxp ffffffffffe05000 00:00 0 ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0 VM Arguments: java_command: org.eclipse.core.launcher.Main -os linux -ws gtk -arch amd64 -showsplash /home/martin/Applications/eclipse/eclipse/./eclipse -showsplash 600 -exitdata /home/martin/Applications/eclipse/eclipse/./eclipse -exitdata 28003 -Xms256m -Xmx512m -vm /home/martin/Applications/Java/jdk1.5.0/bin/java -vmargs -cp /home/martin/Applications/eclipse/eclipse/./startup.jar org.eclipse.core.launcher.Main Environment Variables: JAVA_HOME=/home/martin/Applications/Java/jdk1.5.0 CLASSPATH=. PATH=/home/martin/Applications/Java/jdk1.5.0/bin:/home/martin/Applications/Java/jdk1.5.0/jre/bin:/usr/kde/3.3/bin:/bin:/usr/bin:/usr/local/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/3.4:/usr/X11R6/bin:/opt/blackdown-jdk-1.4.2_rc1/bin:/opt/blackdown-jdk-1.4.2_rc1/jre/bin:/usr/qt/3/bin:/usr/kde/3.3/bin:/usr/kde/3.2/bin:/usr/games/bin:/usr/share/karamba/bin LD_LIBRARY_PATH=/home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64/server:/home/martin/Applications/Java/jdk1.5.0/jre/lib/amd64:/home/martin/Applications/Java/jdk1.5.0/jre/../lib/amd64 SHELL=/bin/bash DISPLAY=:0.0 --------------- S Y S T E M --------------- OS:Gentoo Base System version 1.4.16 uname:Linux 2.6.5-gentoo #1 Fri Jun 4 19:05:43 EDT 2004 x86_64 libc:glibc 2.3.4 linuxthreads-0.10 (floating stack) rlimit: STACK 8192k, CORE 0k, NPROC 8185, NOFILE 1024, AS infinity load average:0.24 0.36 0.23 CPU:total 1 Memory: 4k page, physical 1023136k(163508k free), swap 506036k(506036k free) vm_info: Java HotSpot(TM) 64-Bit Server VM (1.5.0-rc-b63) for linux-amd64, built on Aug 11 2004 02:49:28 by java_re with gcc 3.2.2 (SuSE Linux) REPRODUCIBILITY : This bug can be reproduced often. workaround : suggested_val : cust_name : Jacob Martin cust_email : jmartin@chem.uga.edu jdcid : funtala language : English keyword : webbug company : University of Georgia hardware : itanium OSversion : Linux bugtraqID : 0 dateCreated : 2004-09-03 01:42:00.8 dateEvaluated : 2004-09-03 10:22:05.46 platforms.
They are not saying it is not a VM bug. They ask us to narrow the problem and get back to them. This is much much different. Can you try to disable the JIT ? run with -Djava.compiler=none to see if it changes the problem ? (it will slow down execution)
Well, with the new -Djava.compiler=none, the first java file I tried to open gave me the error: JVM terminated. Exit code=1 /home/martin/Applications/Java/jdk1.5.0/bin/java -cp /home/martin/Applications/eclipse/eclipse/./startup.jar org.eclipse.core.launcher.Main -os linux -ws gtk -arch amd64 -showsplash /home/martin/Applications/eclipse/eclipse/./eclipse -showsplash 600 -exitdata /home/martin/Applications/eclipse/eclipse/./eclipse -exitdata 190003 -Xms256m -Xmx512m -Djava.compiler=none -vm /home/martin/Applications/Java/jdk1.5.0/bin/java -vmargs -cp /home/martin/Applications/eclipse/eclipse/./startup.jar org.eclipse.core.launcher.Main
Created attachment 14761 [details] Newest Crash info with -Djava.compiler=none and SUN1.5.0 RC
This last crash indicates you were running with JIT enabled. Your command line should look like: eclipse.exe -vm /home/martin/Applications/Java/jdk1.5.0/bin/java -vmargs - Xms256m -Xmx512m -Djava.compiler=none Note that -vmargs must be the last option on the command line.
Also, why are you trying to run Eclipse on this beta VM ? A 1.4 VM is sufficient for running Eclipse.
Ok, I'm trying it now with JIT disabled and blackdown 1.4.2_rc. It seems to be working, but the crash is random. I'll update the bug if it happens again. I was using 5.0 because it is the only way I can debug properly. There is another bug around here about not being able to debug with blackdown 1.4.2_rc
Ok, so as far as we are concerned Eclipse does nothing wrong, except expose a bug in some vendor's JIT. This vendor should investigate the issue, since he owns the offending component. Closing as WONTFIX, since no further action is planned.
I have now got the workspace into a mode that always gives me a segfault in several different methods (seemingly random). Maybe this is related to the problems I was having earlier. Here are the methods: alias ibm='source /home/martin/.gentoo/java && cd /home/martin/Applications/eclipse/eclipse && ./eclipse -Xms128m -Xmx512m -Djava.compiler=none' mygentoo martin $ ibm # # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGSEGV (0xb) at pc=0x0000002a99c17918, pid=17768, tid=182899355792 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0-b64 mixed mode) # Problematic frame: # j org.eclipse.jdt.internal.compiler.SourceElementParser.notifyAllUnknownReferences()V+57 # # An error report file with more information is saved as hs_err_pid17768.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # mygentoo eclipse $ pico ~/.bashrc mygentoo eclipse $ source ~/.bashrc mygentoo eclipse $ ibm # # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGSEGV (0xb) at pc=0x0000002a99c10038, pid=17805, tid=182899355792 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0-b64 mixed mode) # Problematic frame: # j org.eclipse.jdt.internal.compiler.SourceElementParser.notifySourceElementRequestor(Lorg/eclipse/jdt/internal/compiler/ast/CompilationUnitDeclaration;)V+160 # # An error report file with more information is saved as hs_err_pid17805.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # mygentoo eclipse $ ibm # # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGSEGV (0xb) at pc=0x0000002a99c16983, pid=17873, tid=182899355792 # # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0-b64 mixed mode) # Problematic frame: # j org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.parseMethod(Lorg/eclipse/jdt/internal/compiler/parser/Parser;Lorg/eclipse/jdt/internal/compiler/ast/CompilationUnitDeclaration;)V+76 # # An error report file with more information is saved as hs_err_pid17873.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # mygentoo eclipse $
Aren't these enough evidences of poor VM on this platform ? Are you suggesting we rewrite our entire component until this buggy VM runs it ok ? First, can you provide steps to reproduce ? And on a different VM ? If so then pls reopen
I think the people at sun need some more information from you guys. Is there a particular call or something that is being executed in each of these different methods? They keep trying to get me to get more information from you somehow... Do none of your amd 64 testers have these problems?
Just an update to let you know that this still happens in 1.5.0_01. It happens here org.eclipse.jdt.internal.compiler.parser.Scanner.optimizedCurrentTokenSource3()[C+186
The offending code has nothing really fancy. Plain Java code, no natives. Eclipse downloads are freely available, so they should be able to reproduce the issue. Note that I suspect they are trying to get you to reduce the testcase, so as not to watch too big a testcase; but this really is their bug. Isn't there another VM you could switch too ?
Thanks for the information, I feel like I'm starting to get out of limbo land. I have tried this with other VMs. Blackdown 1.4.2, and several sun VMs. It happens with every VM I've tried! That's the really weird part. I must confess that I don't have time to build a proper test case. But if I get a chance, I will try to do it for them. Thanks,
FYI - here is the source of the offending method in Scanner: final char[] optimizedCurrentTokenSource3() { //try to return the same char[] build only once char c0, c1, c2; int hash = (((c0 = this.source[this.startPosition]) << 12) + ((c1 = this.source[this.startPosition + 1]) << 6) + (c2 = this.source[this.startPosition + 2])) % TableSize; char[][] table = this.charArray_length[1][hash]; int i = newEntry3; while (++i < InternalTableSize) { char[] charArray = table[i]; if ((c0 == charArray[0]) && (c1 == charArray[1]) && (c2 == charArray[2])) return charArray; } //---------other side--------- i = -1; int max = newEntry3; while (++i <= max) { char[] charArray = table[i]; if ((c0 == charArray[0]) && (c1 == charArray[1]) && (c2 == charArray[2])) return charArray; } //--------add the entry------- if (++max >= InternalTableSize) max = 0; char[] r; table[max] = (r = new char[] {c0, c1, c2}); newEntry3 = max; return r; }
Created attachment 16928 [details] Scanner classfile with offending method slightly changed Out of curiosity, if replacing in jdtcore.jar the classfile for Scanner.class with this one (for M4 build or better), would it change the crash behavior ?
The Scanner change corresponds to the following definition for offending method: final char[] optimizedCurrentTokenSource3() { //try to return the same char[] build only once char[] src = this.source; int start = this.startPosition; char c0 = src[start]; char c1 = src[start+1]; char c2 = src[start+2]; int hash = ((c0 << 12) + (c1<< 6) + c2) % TableSize; char[][] table = this.charArray_length[1][hash]; int i = newEntry3; while (++i < InternalTableSize) { char[] charArray = table[i]; if ((c0 == charArray[0]) && (c1 == charArray[1]) && (c2 == charArray[2])) return charArray; } //---------other side--------- i = -1; int max = newEntry3; while (++i <= max) { char[] charArray = table[i]; if ((c0 == charArray[0]) && (c1 == charArray[1]) && (c2 == charArray[2])) return charArray; } //--------add the entry------- if (++max >= InternalTableSize) max = 0; char[] r; table[max] = (r = new char[] {c0, c1, c2}); newEntry3 = max; return r; }
Created attachment 16990 [details] error log after a crash in gentoo amd64
Aren't all VMs you tried based on HotSpot ? If so, you may hit the same bug all the time. May I suggest you give a try to an alternate VM implementation using a different technology ? You may find one 1.4.2 VM for Linux AMD64 by going to www.ibm.com/developer
I was helping a user debug this problem today on IRC. I wonder if it is really a VM problem since I think there are other users who have been able to successfully use the GTK+/AMD64 version of Eclipse. As both of the users who have reported this problem are using gentoo Linux: could you confirm that this problem also occurs with the eclipse build from eclipse.org and not the gentoo eclipse packages? Trying with the IBM VM is an excellent idea as well.
On other platform, there was also JIT crashes near the Scanner class as well. Looks our implementation is challenging some JITs, likely because it is running in a tight loop with somehow aggressive Java code.
./eclipse -Xms128m -Xmx512m -Djava.compiler=none When I run like this, shouldn't the JIT be disabled? I still get the crashes like this as well.
You need to specify "-vmargs" to the Eclipse application to indicate that subsequent are directed to the VM (rather than to Eclipse application). ./eclipse -vmargs -Xms128m -Xmx512m -Djava.compiler=none
*** Bug 83688 has been marked as a duplicate of this bug. ***
*** Bug 83689 has been marked as a duplicate of this bug. ***
Just to let you know that with the java.compiler=none flag, I am not experiencing any trouble. Very strange to be getting this on multiple VMs
How bad's the performance hit without a JIT? I'm now using IBM's JDK 1.4.2 f/AMD64 and I haven't been hit by this problem, yet. Still I've found other apparently JIT-related crashes, but in my app.
Performance is nasty. Especially when trying to popup complete, or type. Compilation takes forever it seems. You are using blackdown 1.4.2?
Though these are multiple VMs in appearance, both use the same back end (JIT) to provide performance boost: namely Hotspot. By disabling the JIT as you did, the problem is now gone, but performance is poor. Did you try the alternatve 1.4.2 VM for Linux AMD64 (www.ibm.com/developer) which does not use HotSpot if you run it with command line option: "-Xj9".
FYI, With IBM's (not blackdown) 1.4.2, and NOT disabling the hotspot compiler, I have not had any trouble (yet).
To clarify, if you run with "-Xj9" you aren't running Hotspot. Hotspot is the name of Sun JIT, not the IBM one.
*** Bug 86873 has been marked as a duplicate of this bug. ***
Closing this defect, as we do not want to give the false impression we will fix it later. It is some VM vendor bug.
(In reply to comment #40) > Closing this defect, as we do not want to give the false impression we will fix > it later. It is some VM vendor bug. I think nobody expects the Eclipse team to fix this, but to help provide Sun a reduced test case. Of course you don't have to as it's really not your fault, but it would be great to push Sun to fix this before Eclipse 3.1 launches with full support for Java 5. Just my 2¢. I still thank you all for Eclipse :)
(In reply to comment #37) > FYI, With IBM's (not blackdown) 1.4.2, and NOT disabling the hotspot compiler, I have > not had any trouble (yet). Both the Blackdown 1.4 and Sun's 1.5 are giving me this same crash every time I start up eclipse, I'm running debian pure64 on amd64/smp. IBM's 1.4.2 works just fine, no crashes. The sun/blackdown crash occurrs for me in: Function=org.eclipse.jdt.internal.compiler.parser.Scanner.getNextToken()I D-
This also happens to me on a fully patched Fedora Core 3 system running the latest release of JDK5. java version "1.5.0_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-b09) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_02-b09, mixed mode) Linux iron 2.6.10-1.770_FC3 #1 Thu Feb 24 18:09:38 EST 2005 x86_64 x86_64 x86_64 GNU/Linux
To the new people on this bug, try disabling the JIT in your VM: eclipse -vmargs -Djava.compiler=none You can also just get the 32-bit VM and 32-bit eclipse and use this, since the 64-bit VMs from Sun still seem so unstable. Using the IBM VM is another good suggestion.
*** Bug 90797 has been marked as a duplicate of this bug. ***
*** Bug 57141 has been marked as a duplicate of this bug. ***
In bug 57141, Colin Lear points to this bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5101904 and suggests trying different -Xmx parameters to maybe work around the bug.
No, comment #47 is misleading. The workaround suggested in the linked resource is to add -Xint -d64 to the command-line, which effectively disables the JIT and has been already discused in this same report.
I agree that the problem does not occur if you disable JIT. However the suggested method to generate an example of this bug (ctrl click to trace a variable source) did not occur even when I left JIT enabled and only increased the maximum heap size. I can't say that this is a definite workaround. I will probably do more testing during the week when I get back to work. To me this sort of workaround makes as much sense as the JVM being unstable with a max heap of 256meg. However it seems to reduce the incidence of this bug for me at least. This appears to be an issue with the Sun AMD64 VM (1.5.0.02-b9 is what I have) my eclipse.ini (no other options being used) looks like this. -vmargs -Xms40m -Xmx300m I was just looking for other people to test this when I posted in the other bug.
As observed above, fiddling with memory options changes little. Crashes are just random and unpredictable with HotSpot or JIT optimisation enabled. Sometimes they are common other times only occasional. Sorry to waste your time.
Just tried Java 1.5.0_3, same problem. Did anybody consider that the problem could lie in that Sun is using the GCC 3.2.x compiler? From what I read at the Debian AMD64 mailing list, GCC before 3.3.x does not produce very good results on AMD64. Unfortunately GCC 4.0 is still quite buggy, and I don't know about GCC 3.4. As for 3.3.x, I'm running a full 64-bit Linux desktop/development system compiled with it, and like me there are hundreds or thousands of others. Maybe we should suggest Sun to update their compiler and see what turs out?
I'm sorry to reply to myself, but I just found out that it's very unlikely that Sun would agree to do what I suggested: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4955492 .
*** Bug 76957 has been marked as a duplicate of this bug. ***
I was aborting pretty regulary until I tried -Xss512k on the eclipse command line. It might be too early to tell yet, but that does seem to make sense. (Your stack usage would frequently double in size since object references are now 64 bits)
Oops, just crashed on me even with the -Xss512k. Sorry for the spam.
When I increased the stack size to 512k on both eclipse and the application I am running, I have gone an entire day with no crash in full mixed mode. My eclipse.ini reads: -vmargs -d64 -Xss512k -Xms1024m -Xmx1024m
Remember that Eclipse only requires a 1.4 level JRE, so the switch to another VM to host Eclipse application is all you need to workaround the JVM bug. See comment 26. Running Eclipse on some 1.4 JRE has no consequences on the fact it can handle 1.5 development. You will simply have to an extra install a 1.5 JRE (check Window>Preferences>Java>Installed JREs) to perform the setup.
(In reply to comment #57) > Remember that Eclipse only requires a 1.4 level JRE, so the switch to another VM > to host Eclipse application is all you need to workaround the JVM bug. See > comment 26. > > Running Eclipse on some 1.4 JRE has no consequences on the fact it can handle > 1.5 development. You will simply have to an extra install a 1.5 JRE (check > Window>Preferences>Java>Installed JREs) to perform the setup. Yes but that removes the whole point of running Eclipse in 1.5; the fact that the 1.5 JRE has an amd64 version with 64 bit optimisations. I think this is the only reason that people want to run Eclipse on 1.5 when, as the bug describes, is on an amd64 machine.
*** Bug 97112 has been marked as a duplicate of this bug. ***
*** Bug 102579 has been marked as a duplicate of this bug. ***
I'm just wondering, if we are all experiencing this as Debian/Gentoo users, could it have something to do with NPTL being on? I saw in IBM's jdk that they have factored NPTL in their architecture, I wonder if Sun/Blackdown hasn't??
The stack size arguments in Comment 56 do not help me. The bug seems to happen when the workspace gets into a bad "state". If I delete the workspace, then it will work fine for a while. I did just see a Scanner.getNextToken() error on the last 3.1 RC. I'll try again on the new final release. The nptl idea in Comment 61 is very intriguing, perhaps someone can test. I may should note that I have very big projects (several thousands of source files).
FWIW I have the same issue using SuSE Linux 9.3 64-bit on an AMD64, with the latest 64 bit JDK 1.5.0_03-b07. Increasing stack and memory sizes does not help. The hotspot error log always mentions Scanner.getNextToken() or Scanner.jumpOverMethodBody().
(In reply to comment #63) > FWIW I have the same issue using SuSE Linux 9.3 64-bit on an AMD64, with the > latest 64 bit JDK 1.5.0_03-b07. The latest JDK is actually update 4 from late June, which fixes some 64-bit and hotspot related issues. It seems to run more stably on Linux than update 3, although I still see the occasional crash. Also, "With the release, J2SE support for Windows 64-bit has progressed from release candidate to final release. This version runs on AMD64/EM64T 64-bit mode machines with Windows Server 2003 x64 Editions." http://java.sun.com/j2se/1.5.0/ReleaseNotes.html
Just wanted to clarify that the bug never seems to happen with IBM's 1.4.2 AMD 64 JDK Also, all of the reports I have made have been without disabling the JIT and using some VM other than IBM's.
*** Bug 102845 has been marked as a duplicate of this bug. ***
I'm running debian sid amd64 and i experience the same problem, each time i open a file in eclipse 3.1, eclipse crashes.
(In reply to comment #67) > I'm running debian sid amd64 and i experience the same problem, each time i open > a file in eclipse 3.1, eclipse crashes. I'm an Engineer at Sun, and I've been trying to reproduce this bug for a long time with no success. I have a 4 processor Opteron machine running Red Hat Enterprise 4.0, and I've tried all sorts of Eclipse builds and I've never had it crash. If someone emails me, maybe we can work through this and attempt to reproduce and eventually fix this. Email me at azeem dot jiva at sun dot com. Thanks(In reply to comment #67) > I'm running debian sid amd64 and i experience the same problem, each time i open > a file in eclipse 3.1, eclipse crashes.
(In reply to comment #68) Thanks for the attention to this matter. The bug seems random, but seems to happen more often when you have a really big project. To make it happen, try invoking the code assist, open lots of java source files, rebuild the project, etc. I remember it happening a lot when trying to open new files. Good luck! It is very random, but once you get the workspace into a "bad" state, you should be able to reproduce it constantly. Once you get it to this point, eclipse will exit right after you start and you'll have to delete the workspace to make it start properly again.
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 Since its a dot file, it'll be hidden from ls, etc so remember to remove it when I do get this fixed :) Performance should be much better than the interpreter.
Doh the file didn't come out right, but basically the excludes are one line long and not on two lines. There is a space after Scanner and optimized (In reply to comment #71) > 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 > > > Since its a dot file, it'll be hidden from ls, etc so remember to remove it when > I do get this fixed :) Performance should be much better than the interpreter. >
Azeem, Just letting you know I'm also frequently getting the crashing out with Eclipse. Before now I've just been deleting the .metadata directory and letting it refresh the workspace which usually makes it ok for another 5 goes! I'll give your workaround of creating the .hotspot file a go though. If you need any more specific information please let me know. Thanks _HEAPS_ for all of your good work on this. Michael
Another idea: The eclipse gtk version depends on gnome stuff. The same time eclipse crashes, I had similar problems with the gnome-control-center. I use it for setting the fonts of my eclipse ide. After some trial and error I removed the gnome-control-center, gnome-control-center2 (and because of following conflicts: gdm, gnome-utils...) from my system (SuSE 9.3). After this, I could start eclipse again. I couldn't find out what libs are causing the problem, but I guess that some of them may have changed to incompatible versions by installing some new tools. Of cause, this is just a crude workaround but my help for a real solution.
Do you still have the crash log for that problem? If so, please open a new bug with the log. I suspect that is a different issue than this bug.
Count me into the mix of users having this issue. I am able to recreate using the Blackdown JDK 1.4.2 as well as recent releases of the Sun 1.5 JDK. I can tell you what action triggered it on my system, if it helps. I have been working in Eclipse all week with no problems at all. However, this morning I tried opening one of the "closed" projects in my workspace. The project opened, but within 5 seconds Eclipse had the crash. ** From this point onward, Eclipse crashes whenever I open certain files in my editor, from any project in this workspace -- even if I remove the project that I opened before the crash. ** I've had this problem in the past and it frequently triggers from opening and closing projects in a workspace. However, the error seems to corrupt the state of the workspace somehow, because once it starts it continues to happen.
*** Bug 103147 has been marked as a duplicate of this bug. ***
Created attachment 25886 [details] Crash in AMD64 Crash using WBLE and JDK 1.5.0_04 Eclipse 3.1.0 I20050627-1435
(In reply to comment #65) > Just wanted to clarify that the bug never seems to happen with IBM's 1.4.2 AMD 64 > JDK Thanks for this work-around. I am now using the IBM 1.4.2 (64-bit) JDK on my system and all is well. **ANYONE STILL HAVING THIS HORRIBLE PROBLEM: I recommend a switch to the IBM JDK. I am unable to reproduce the problem at all on this JDK. Another note: On Sun 1.4/1.5 JDK's, as well as Blackdown 1.4, I can reproduce this problem with a non-NPTL system, as well as a freshly built NPTL system. Therefore, we can probably rule out NPTL as being related (at least directly).
> Thanks for this work-around. I am now using the IBM 1.4.2 (64-bit) JDK on my > system and all is well. **ANYONE STILL HAVING THIS HORRIBLE PROBLEM: I > recommend a switch to the IBM JDK. The problem is that I'm working using <1.5.0> new features, so I'm not able to change to IBM 1.4.2.
(In reply to comment #80) > The problem is that I'm working using <1.5.0> new features, so I'm not able to > change to IBM 1.4.2. No! If you're running eclipse with Java2 you are able to use Java5-Features. It's just a matter of the setting in Preferences->Java->Installed JRE's, this will be the version eclipse uses for compile, it can differ from the version eclipse is running with. But question: To get the IBM-JDK i have to register or something like that, haven't I?
(In reply to comment #81) > But question: To get the IBM-JDK i have to register or something like that, > haven't I? It depends. Some Linux distros already package it for you. Check your package management system, if your distro has one. Otherwise, yes, you will need to download it from IBM's DeveloperWorks site, which requires an IBM (Universal) ID. Registration is free. I did some digging and the current download URL's are here: http://www.ibm.com/developerworks/java/jdk/index.html
Prompted by Azeem Jiva of Sun I've been running with a Sun Java6 JVM on AMD64 for a while now without any crashing. Weekly Java6 builds can be downloaded at https://mustang.dev.java.net/.
*** Bug 107520 has been marked as a duplicate of this bug. ***
*** Bug 108909 has been marked as a duplicate of this bug. ***
*** Bug 109032 has been marked as a duplicate of this bug. ***
I tried to download the IBM JRE but this is impossible. After answering several questions about personal information it simply says: Download Director applet cannot be loaded. Java support must be enabled to run. If I had a working Java VM, I would not try to download one.
(In reply to comment #87) > I tried to download the IBM JRE but this is impossible. After answering several > questions about personal information it simply says: > > Download Director applet cannot be loaded. > Java support must be enabled to run. > > If I had a working Java VM, I would not try to download one. This is not the place for IBM Java support, however, you'll find there are two methods of downloading software from IBM: Download Director and normal FTP. In your case you should choose FTP. Or, of course, you could download Sun Hicrosystems Java implementation. I hear it works pretty well.
*** Bug 106722 has been marked as a duplicate of this bug. ***
*** Bug 111443 has been marked as a duplicate of this bug. ***
I didn't see any reference to SUNs 1.5.0_04-b05, and yes, it suffers the same problem. So did an early release of Mustang I had (just downloaded to see how it works). On the plus side, the IBM 1.4.2 VM is noticeably faster and didnt die when I tried to load the eclipse 3.1 source project Id built under win32! I also need to try the IBM 1.5beta. Looks like IBM have stolen a march on SUN here...
If you want to folow the bug's evolution from the JDK's side, it is #5060628 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5060628 Cheers
*** Bug 112738 has been marked as a duplicate of this bug. ***
*** Bug 113648 has been marked as a duplicate of this bug. ***
Anyone want to test a fix for this bug?
(In reply to comment #95) > Anyone want to test a fix for this bug? I'm probably game for this. What are the details? I'm sure many folks here would try it out.
Easiest way is to grab: www.csc.calpoly.edu/~ajiva/libjvm.so.gz gunzip the file and put it: <JAVA_HOME/jre/lib/amd64/server You'll need to have the latest Java6 release, but otherwise it should fix the problem.
It would be nice to have a patch for the latest 1.5 VM available on Linux.
(In reply to comment #98) > It would be nice to have a patch for the latest 1.5 VM available on Linux. There will be an official one later, but for now this is just to test and make sure the problem goes away. You can try over copying the file to a JAVA5 JDK, but make sure you save the old file in case things break.
(In reply to comment #97) > gunzip the file and put it: > > <JAVA_HOME/jre/lib/amd64/server > > You'll need to have the latest Java6 release, but otherwise it should fix the > problem. My testing report: So far, so good. :-) I don't have a Java6 runtime currently installed... Therefore I decided to test this on a Java5 release (1.5.0.05). So far, I am NOT able to reproduce any problems... even in Eclipse workspaces that were already having the problem in the past. I've also been testing other Java-based applications just for compatibility of your patch with the Java 5 runtime. I'm not seeing any problems there yet, either. I'll keep using this and report back if I notice any problems. Thanks!
(In reply to comment #97) > Easiest way is to grab: > www.csc.calpoly.edu/~ajiva/libjvm.so.gz > gunzip the file and put it: > <JAVA_HOME/jre/lib/amd64/server > You'll need to have the latest Java6 release, but otherwise it should fix the > problem. Yes, the patch seems to work. I can´t reproduce the error. Thanks.
I just encountered a similar problem after upgrading to 64bit Linux and after much hair pulling was about to install the IBM 1.4.2 jdk when I ran across this thread. Patch works for me running against mustang release b58 (both the jvm running eclipse and the "workspace jvm"). I have not tried other jvm releases or configurations. FWIW, I am running SuSE 10.0 x86_64 on a Compaq Presario R3000 laptop, AMD64 3000+, 2G RAM, kernel 2.6.13. Eclipse version is: 3.1.1 Build id: M20050929-0840 Thanks Azeem!
Ok the bug fix will be in Mustang B59 and Java5 update 6, thanks for your patience with this :) Oh and see my blog for more info about what the problem was. It was only a two line fix (yeah that simple). http://blogs.sun.com/javawithjiva
*** Bug 114564 has been marked as a duplicate of this bug. ***
*** Bug 116243 has been marked as a duplicate of this bug. ***
*** Bug 102490 has been marked as a duplicate of this bug. ***
*** Bug 144150 has been marked as a duplicate of this bug. ***
Sorry for probably offtopic question, but I've noticed that each time followed threads seems to be in the VM dumps: - Low Memory Detector - CompilerThread1 - CompilerThread0 - AdapterThread These threads are normally not started in the VM, and as AFAIK the first one is started if VM memory goes low. Does anybody have any idea who starts other three threads and why? Could it be related to bug 163174 comment 9? I completely agree that there could be an VM or JIT implementation problem, but I'm currently looking for the *working* solution for the RHEL release 3 & Sun JDK 1.5.0_03 & Eclipse 3.1.1 - 3.2.1.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
