-
Enhancement
-
Resolution: Fixed
-
P4
-
7
-
b01
-
generic
-
generic
-
Not verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2200266 | 7 | Tomáš Hůrka | P4 | Closed | Fixed | b112 |
| JDK-2205958 | 6u25 | Tomáš Hůrka | P4 | Closed | Fixed | b01 |
The hotspot built-in heap dumper now includes the stack traces in the heap dump (see 6306922).
The OutOfMemoryError is preallocated by the VM and the stack trace is filled after the heap dump. So the stack traces have no indication which thread is throwing the OOME.
It would be very helpful for diagnosing the OOME problem if tools like VisualVM can show which thread throwing OOME from the heap dump when +HeapDumpOnOutOfMemoryError is set.
The OutOfMemoryError is preallocated by the VM and the stack trace is filled after the heap dump. So the stack traces have no indication which thread is throwing the OOME.
It would be very helpful for diagnosing the OOME problem if tools like VisualVM can show which thread throwing OOME from the heap dump when +HeapDumpOnOutOfMemoryError is set.
- backported by
-
JDK-2200266 Indicate which thread throwing OOME when generating the heap dump at OOME
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-