Java VM crashed with insufficient memory "Native memory allocation (malloc) failed to allocate XXXX bytes for CodeCache: no room for vtable chunks"

Solution In Progress - Updated -

Issue

Java VM crashed with insufficient memory "Native memory allocation (malloc) failed to allocate XXXX bytes for CodeCache: no room for vtable chunks". Java VM crash report hs_err_pid<PID>.log contained the followings:

#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 4104 bytes for CodeCache: no room for vtable chunks
# Possible reasons:
#   The system is out of physical RAM or swap space
#   In 32 bit mode, the process size limit was hit
# Possible solutions:
#   Reduce memory load on the system
#   Increase physical memory or swap space
#   Check if swap backing store is full
#   Use 64 bit Java on a 64 bit OS
#   Decrease Java heap size (-Xmx/-Xms)
#   Decrease number of Java threads
#   Decrease Java thread stack sizes (-Xss)
#   Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
#  Out of Memory Error (vtableStubs.cpp:63), pid=24592, tid=139852319278848
#
# JRE version: 6.0_45-b06
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.45-b01 mixed mode linux-amd64 compressed oops)

Environment

  • Java

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In