The post explains how to obtain a heap dump on OutOfMemoryError with Quarkus native using the `-XX:+HeapDumpOnOutOfMemoryError` option. It compares the heap dump of a GraalVM Native Image with one produced by HotSpot and discusses the presence of SubstrateVM classes in the heap dump.

•7m read time•From quarkus.io
Post cover image
Share this post