Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6765718

Indicate which thread throwing OOME when generating the heap dump at OOME

    Details

    • Type: Enhancement
    • Status: Closed
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 7
    • Fix Version/s: hs20
    • Component/s: hotspot
    • Subcomponent:
      svc
    • Resolved In Build:
      b01
    • CPU:
      generic
    • OS:
      generic
    • Verification:
      Not verified

      Backports

        Description

        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.

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  thurka Tomáš Hůrka
                  Reporter:
                  mchung Mandy Chung
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Imported:
                    Indexed: