|
|
# Possible reasons:7 v9 A7 ]% T; M8 [/ S% J" n- G
# The system is out of physical RAM or swap space
- C( @: V! J9 d! S {, s6 g1 `# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap% Z$ t7 p, E3 ?, G8 a
# Possible solutions:# K4 G! q& l8 p) ^; Q: m1 p
# Reduce memory load on the system
7 d9 `1 H; @8 z, m& ?# Increase physical memory or swap space
u l+ m0 |9 N) F# Check if swap backing store is full
) l3 _; l$ d- Z, ?$ E$ @5 W# Decrease Java heap size (-Xmx/-Xms)
2 e) e4 W3 ~' T/ P# Decrease number of Java threads
5 e# Y8 A3 n1 W4 E7 @ E# Decrease Java thread stack sizes (-Xss)
- E! ]( j9 d+ x9 @7 d9 R" B/ j8 F# Set larger code cache with -XX:ReservedCodeCacheSize=
7 a( t* I2 P1 O) v, n# JVM is running with Zero Based Compressed Oops mode in which the Java heap is" n- G, _! z) k2 A' x
# placed in the first 32GB address space. The Java Heap base address is the
3 C% Z& D+ s8 R" _$ w; d# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
6 k5 `' x2 W" d5 e6 ?1 E# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
7 C8 h6 o% F/ l; I& [6 s8 n% r6 o把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主