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

Limit the number of heap dumps triggered by HeapDumpBeforeFullGC/AfterFullGC

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • 23
    • None
    • hotspot
    • None
    • svc
    • b05

      When encountering FGC, HeapDumpBeforeFullGC/AfterFullGC are commonly enabled to help with troubleshooting.

      In the current implementation, unlike HeapDumpOnOutOfMemoryError, which will only generate one dump, these two flags will generate dumps for every FGC, increasing the risk of disk full.

      Although these two flags are manageable, disabling them timely in production may not be easy.

      To enhance production-friendliness, it would be beneficial to have the ability to limit the number of dumps triggered by these two flags.

            ddong Denghui Dong
            ddong Denghui Dong
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: