Java VM crashed with insufficient memory "Native memory allocation (malloc) failed to allocate XXXX bytes for PSOldGen::expand_to_reserved"

Solution Unverified - Updated -

Issue

  • JVM crashed where hs_err_pid<PID>.log contained the following:
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 4194304 bytes for PSOldGen::expand_to_reserved
# Possible causes:
#   - not enough swap space left, or
#   - kernel parameter MAXDSIZ is very small.
# 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 (psOldGen.cpp:313), pid=1117, tid=132
#
# JRE version: 6.0
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.65-b04-jre1.6.0.21-rc1 mixed mode hp-ux-ia64 )

---------------  T H R E A D  ---------------

Current thread (6000000000dc4400):  JavaThread "ServerService Thread Pool -- 88" [_thread_in_vm, id=132, lwp_id=4858111, stack(9fffffff12b81000,9fffffff12c01000)]

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.2.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content