|
|
# Possible reasons:
W1 J! E3 [) K |6 A1 M- q9 ~( G# The system is out of physical RAM or swap space9 y8 e) u- f7 t
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
6 B4 H5 g8 K( q# Possible solutions:
, b# t! b8 h" Q' i9 @# Reduce memory load on the system& U$ K" s4 W# P7 Q5 _# x5 \& H
# Increase physical memory or swap space
$ A+ k% B: @ x* c3 ]# Check if swap backing store is full, z0 u! ]4 c3 N
# Decrease Java heap size (-Xmx/-Xms)
; l1 p5 h" i$ F n9 V" b4 C( S# Decrease number of Java threads$ Z- G5 j# M% u8 L
# Decrease Java thread stack sizes (-Xss)) J J8 S1 W: V* l/ [3 O! r
# Set larger code cache with -XX:ReservedCodeCacheSize=; I0 l2 W- K, {' R; J
# JVM is running with Zero Based Compressed Oops mode in which the Java heap is9 w" k: @" f" r4 K8 n1 C3 k0 B
# placed in the first 32GB address space. The Java Heap base address is the
. C- N- h# I% i, z# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
: P( H/ r3 |8 Z, F: Y0 ]: J* J# to set the Java Heap base and to place the Java Heap above 32GB virtual address. P* ^# U1 c9 G
把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主