RFR: JDK-8322042: HeapDumper should perform merge on the current thread instead of VMThread [v2]

Alex Menkov amenkov at openjdk.org
Tue Apr 2 21:13:33 UTC 2024


On Tue, 2 Apr 2024 02:04:17 GMT, Yi Yang <yyang at openjdk.org> wrote:

> * jcmd GC.heap_dump command; `AttachListenerThread`
> 
>     * HotSpotDiagnosticMXBean.dumpHeap(); `JavaThread`
> 
>     * HeapDumpBeforeFullGC, HeapDumpAfterFullGC VM options; `VMThread`
> 
>     * HeapDumpOnOutOfMemoryError VM option. `VMThread`
>       Mabye we can always use AttachListenerThread(via Handshake) or new virtual thread?

AttachListenerThread may not exist (it's created on demand).
Heap dump for HeapDumpOnOutOfMemoryError is performed on the current java thread.
I'm not sure I follow the proposal. What if the profit in using separate thread for merging?

-------------

PR Comment: https://git.openjdk.org/jdk/pull/18571#issuecomment-2033101158


More information about the hotspot-runtime-dev mailing list