java heap dump is not getting generated

Question

not getting java heap dump on outofmemoryerror: Tried this (one.exe is my java rcp app):

one.exe -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:\Temp

but didn't help, the folder path is accessible. I even tried giving name like heap.hprof, but with no result. Can someone guide me here ?

Are those properties getting passed to your underlying JVM ? — Brian Agnew, May 07 '13 at 10:32
jdk version is jdk1.6.0_21 What I did was, navigate to my rcp app directory in command prompt, ie. C:\ProgramFiles\One\one.exe -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:\Temp — user1782807, May 07 '13 at 10:59

score 2 · Answer 1 · answered Sep 24 '20 at 12:34

2

Some thrown heap overflows are not real overflows, but are thrown directly after calculation. In fact, there is no overflow. such as DirectByteBuffer（use allocateMemory）

answered Sep 24 '20 at 12:34

DeepFeeling1999

41
7

score -2 · Answer 2 · answered Apr 23 '15 at 05:36

-XX:+HeapDumpOnOutOfMemoryError Command-line Option If you specify the -XX:+HeapDumpOnOutOfMemoryError command-line option, and if an OutOfMemoryError is thrown, the VM generates a heap dump

This above argument says it will generate HeapDump when OOM is thrown. If the JVM argument is passed to JVM and no heap dump got generated then it implies the application yet to suffer OutOfMemory condition.If you need confirmation then take native stderr log file of the application to check did application suffers any OOM? or include -verbose:gc jvm argument and collect verbose logs and check the last cycle of the GC to check the free bytes of the java heap.

java heap dump is not getting generated

2 Answers2