Limit the number of heap dumps generated by HeapDumpBeforeFullGC/AfterFullGC

[Denghui Dong]

Hi team,
HeapDumpBeforeFullGC/AfterFullGC are the two flags that are commonly used by developers when analyzing FGC problems.
The current implementation of these two flags is triggering a heap dump when every FGC happens.
Although these two flags can be turned off through jinfo, this behavior may still bring trouble(make the disk full) when FGC continuously occurs
Unklie HeapDumpBeforeFullGC/AfterFullGC, HeapDumpOnOutOfMemoryError will only generate one dump.
IMHO, we should improve the implementation.(e.g. Introducing a counter or interval to limit the number).
What do you think?
I'm sorry in advance if this issue has ever been discussed.
Thanks,
Denghui
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20231117/a76f6391/attachment.htm>