Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2177306 | 7 | Unassigned | P3 | Closed | Won't Fix | |
JDK-2172783 | 6u14 | Mandy Chung | P3 | Resolved | Fixed | b01 |
The dump file produced by +HeapDumpOnOutOfMemoryError when OutOfMemoryError is thrown includes stack roots (both locals and JNI locals). These locals are emitted to the dump with an empty stack trace. It would be desirable to emit the stack trace all threads so that the stack roots could be better understood.
This work is also related to the new heap snapshot format that we hope to include in JDK 7, see
https://heap-snapshot.dev.java.net/
for more information.
This work is also related to the new heap snapshot format that we hope to include in JDK 7, see
https://heap-snapshot.dev.java.net/
for more information.
- backported by
-
JDK-2172783 Dump dump created by +HeapDumpOnOutOfMemoryError should include stack traces for stack roots
-
- Resolved
-
-
JDK-2177306 Dump dump created by +HeapDumpOnOutOfMemoryError should include stack traces for stack roots
-
- Closed
-
- relates to
-
JDK-6760477 SA: Update SA to include stack traces in the heap dump
-
- Resolved
-
-
JDK-6759840 Update jhat to include a thread dump
-
- Closed
-
-
JDK-6765718 Indicate which thread throwing OOME when generating the heap dump at OOME
-
- Closed
-