| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2040148 | 1.4.0 | Hui Huang | P4 | Closed | Fixed | beta |
As seen in bug report 4403332, the fatal error handler correctly caught
a crash signal in native code outside VM. But itself died on an assertion
failure while trying to print a stack trace. The last part of the error
report (after "Current Java Thread:") is about this failure and it shouldn't
be printed out. Most likely, the first crash messed up the stack and caused
this assertion failure. Printout of this assertion failure makes it look like
the VM dies because of a bug inside JVM and might mislead users to file a VM
bug.
this bug affects ladybird and merlin.
a crash signal in native code outside VM. But itself died on an assertion
failure while trying to print a stack trace. The last part of the error
report (after "Current Java Thread:") is about this failure and it shouldn't
be printed out. Most likely, the first crash messed up the stack and caused
this assertion failure. Printout of this assertion failure makes it look like
the VM dies because of a bug inside JVM and might mislead users to file a VM
bug.
this bug affects ladybird and merlin.
- backported by
-
JDK-2040148 error handler crashed in bug 4403332 and prints misleading information
-
- Closed
-