|
|
# Possible reasons:
+ h; X4 \9 v b" i2 T) M7 l' V* W# The system is out of physical RAM or swap space2 q) n# P, j& S% x' B+ f/ W
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
' l2 w6 u/ j" y3 W! P1 h6 x% z, E# Possible solutions:& M/ B6 I1 N1 U% z* v, M% h
# Reduce memory load on the system
6 k; u _- o; T( ~# Increase physical memory or swap space
+ H% {( Q1 A& k/ A2 w# Check if swap backing store is full: X2 ]* f5 ]( p2 Y: i
# Decrease Java heap size (-Xmx/-Xms)$ m, W. p: y- d' ]/ S
# Decrease number of Java threads# k. V# t2 U5 r' u; E6 O2 A
# Decrease Java thread stack sizes (-Xss)
* I% I$ ]( |/ }+ S# Set larger code cache with -XX:ReservedCodeCacheSize=1 Y4 j1 ^- d6 z3 j
# JVM is running with Zero Based Compressed Oops mode in which the Java heap is
0 k1 R4 j9 a' g" m1 x6 u# placed in the first 32GB address space. The Java Heap base address is the
+ M9 J' h5 B2 B% i- J& v+ \3 Y' v( A# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress0 `' s6 s8 |( P0 N9 v4 I
# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
- T$ T/ S I' @% u5 Z' ?把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主