Article - CS366183
Run xconfmanager command to update White list wvs.properties with Out of Memory Error
Modified: 29-Mar-2022
Applies To
- Windchill PDMLink 12.0
Description
- Run xconfmanager command to update White list wvs.properties with Out of Memory Error：
There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 54525952 bytes for Failed to commit area from 0x0000000710000000 to 0x0000000713400000 of length 54525952.
# Possible reasons:
# The system is out of physical RAM or swap space
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# JVM is running with Zero Based Compressed Oops mode in which the Java heap is
# placed in the first 32GB address space. The Java Heap base address is the
# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
# This output file may be truncated or incomplete.
#
# Out of Memory Error (./open/src/hotspot/os/windows/os_windows.cpp:3275), pid=8972, tid=6292
#
# JRE version: Java(TM) SE Runtime Environment 18.9 (11.0.8+10) (build 11.0.8+10-LTS)
# Java VM: Java HotSpot(TM) 64-Bit Server VM 18.9 (11.0.8+10-LTS, mixed mode, tiered, compressed oops, g1 gc, windows-amd64)
# Core dump will be written. Default location: C:\ptc\Windchill_12.0\Windchill\hs_err_pid8972.mdmp
# Native memory allocation (mmap) failed to map 54525952 bytes for Failed to commit area from 0x0000000710000000 to 0x0000000713400000 of length 54525952.
# Possible reasons:
# The system is out of physical RAM or swap space
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# JVM is running with Zero Based Compressed Oops mode in which the Java heap is
# placed in the first 32GB address space. The Java Heap base address is the
# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
# This output file may be truncated or incomplete.
#
# Out of Memory Error (./open/src/hotspot/os/windows/os_windows.cpp:3275), pid=8972, tid=6292
#
# JRE version: Java(TM) SE Runtime Environment 18.9 (11.0.8+10) (build 11.0.8+10-LTS)
# Java VM: Java HotSpot(TM) 64-Bit Server VM 18.9 (11.0.8+10-LTS, mixed mode, tiered, compressed oops, g1 gc, windows-amd64)
# Core dump will be written. Default location: C:\ptc\Windchill_12.0\Windchill\hs_err_pid8972.mdmp
This is a printer-friendly version of Article 366183 and may be out of date. For the latest version click CS366183