-
Bug
-
Resolution: Fixed
-
P3
-
6
-
b59a
-
generic
-
generic
The test case below "hangs" the JVM (as expected). The future task has not been submitted to any executor and so get() call blocks.
import java.util.concurrent.*;
public class f {
public static void main(String[] args) throws Exception {
FutureTask f = new FutureTask(new Callable() {
public Object call() {
return "jhvfdjg";
}
});
System.out.println(f.get());
}
}
After JVM blocks, pressing ctrl-\ on Solaris (or ctrl-break on Windows) crashes JVM.
Please refer to the attached hs_errXXX files (on Solaris and Windows). In both platforms, the Java stack traces were printed and crash occurred after that. I used Mustang build-56 on both platforms.
import java.util.concurrent.*;
public class f {
public static void main(String[] args) throws Exception {
FutureTask f = new FutureTask(new Callable() {
public Object call() {
return "jhvfdjg";
}
});
System.out.println(f.get());
}
}
After JVM blocks, pressing ctrl-\ on Solaris (or ctrl-break on Windows) crashes JVM.
Please refer to the attached hs_errXXX files (on Solaris and Windows). In both platforms, the Java stack traces were printed and crash occurred after that. I used Mustang build-56 on both platforms.
- duplicates
-
JDK-6341338 JNLP Appln crashes on RHAS4.0/Cinnabar when DumpThreadStack (key "v") is pressed on java console
- Closed
- relates to
-
JDK-6348268 PIT :nsk/stress/strace/strace006 crashes with SIGSEGV (0xb) at pc=0xca0ef7ed, pid=11925, tid=3 error
- Closed