jni - Does not Java create heapdump when native allocation fails -


the jvm started using parameter -xx:+heapdumponoutofmemoryerror. not creating heapdump on outofmemory.

does not java create heapdump when native allocation fails?

following log:

# there insufficient memory java runtime environment continue. # native memory allocation (malloc) failed allocate 1184288 bytes chunk::new # error report file more information saved as: # d:\product\bin\hs_err_pid5876.log java.lang.outofmemoryerror 

--edit--

the max heap size set 4gb, system ram size 16gb , when ran out of memory using >11gb (shown windows task manager).

from discussion @alain.janinm.... think can conclude jvm didn't have enough memory generate heapdump.

so, possible creating heapdump had caused jvm use system memory

according error java.lang.outofmemoryerror has been thrown. rest of stacktrace indicate happened in native heap. hence allocation failure detected in jni or native method rather in java vm code. (from troubleshooting memory leaks)

that why no heap dump created. according xx:+heapdumponoutofmemoryerror documentation :

the -xx:+heapdumponoutofmemoryerror command-line option tells hotspot vm generate heap dump when allocation java heap or permanent generation cannot satisfied.

because allocation failed in native heap , not java heap, no dump has been created.


Comments

Popular posts from this blog

matlab - "Contour not rendered for non-finite ZData" -

delphi - Indy UDP Read Contents of Adata -

javascript - Any ideas when Firefox is likely to implement lengthAdjust and textLength? -