|
|
# Possible reasons:9 K9 |- V$ D2 \! q: \
# The system is out of physical RAM or swap space
8 _& a p$ D5 P N! S& w; f6 Y# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap2 u3 \4 V& h' _+ N, [9 k# x3 [! K9 k
# Possible solutions:
, [: _6 u! c1 i( U/ X6 L1 i2 g# Reduce memory load on the system7 U+ S1 f3 j& {% F4 @# Y
# Increase physical memory or swap space
$ Q9 l5 Q9 }5 U# Check if swap backing store is full4 d! T" {6 ~3 x8 L* O t! q3 Z
# Decrease Java heap size (-Xmx/-Xms): i0 a D$ c" c5 k( {" T& g3 N+ C. e
# Decrease number of Java threads |7 x5 J! e* K3 Q4 u9 D, f
# Decrease Java thread stack sizes (-Xss)
: c+ p; O: G% f- a0 Y9 O# Set larger code cache with -XX:ReservedCodeCacheSize=( t. k6 K. q% s8 n
# JVM is running with Zero Based Compressed Oops mode in which the Java heap is
' i |( J" X; G) G( H; n9 d# placed in the first 32GB address space. The Java Heap base address is the
9 g, D4 z! Z K- E8 ]# ], b# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress5 k; m9 \' D% m: i( |& t: J b
# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
( R' |3 T& Q7 ]/ n4 \; L9 H把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主