|
|
# Possible reasons:1 i* d% N! r/ N8 W) y3 A
# The system is out of physical RAM or swap space ^7 S* I9 e7 Z0 M& C
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap/ ^/ L' J2 w, m9 b
# Possible solutions:% k9 U( a* B7 p; l7 s) o
# Reduce memory load on the system1 u! x( w, u% y7 s8 \+ x# N7 U
# Increase physical memory or swap space7 R) ?. o3 ^. x- ^ a& R1 K
# Check if swap backing store is full2 Y! C9 B. W7 u
# Decrease Java heap size (-Xmx/-Xms)$ J( R- `) I2 O+ a. O7 C/ o
# Decrease number of Java threads
- X* P1 w5 f R" a) a# Decrease Java thread stack sizes (-Xss)- H3 H: j- w' L( g6 a/ F. ~; T) ^( l
# Set larger code cache with -XX:ReservedCodeCacheSize=
. z5 c. L" b, q" ]# JVM is running with Zero Based Compressed Oops mode in which the Java heap is) P* k+ f7 _+ J! s+ B
# placed in the first 32GB address space. The Java Heap base address is the
$ a2 c" V) O( t$ |0 w# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
9 F4 Q I. T$ j# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
3 |. }7 i p( t" M+ c' e6 A# j把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主