|
|
# Possible reasons:+ C8 k: l4 d" I( ]' z
# The system is out of physical RAM or swap space
3 t- R1 A# \ h4 g- n# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap8 I1 d; X6 h8 o: B, \# O
# Possible solutions:/ p! t" H* a4 _& p6 V& q" F$ Y
# Reduce memory load on the system
7 p: v) Z# f7 \6 A6 O0 H# Increase physical memory or swap space6 u" m' M3 T. X) R+ a
# Check if swap backing store is full- x# j) Y4 p+ c1 s: H, c
# Decrease Java heap size (-Xmx/-Xms)) Q1 \1 T4 w9 J
# Decrease number of Java threads' N! x5 Q4 p0 [
# Decrease Java thread stack sizes (-Xss)3 H9 d- }' O. J& |, N
# Set larger code cache with -XX:ReservedCodeCacheSize=4 r' p7 n7 E. D6 r9 K
# JVM is running with Zero Based Compressed Oops mode in which the Java heap is3 q$ o9 ]9 p! a6 ~5 F" @: k3 I
# placed in the first 32GB address space. The Java Heap base address is the! c) r; C7 T7 z! d+ |4 Y& ~
# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress; b+ h5 P d: E6 }3 C# l: e
# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
3 j6 v/ U+ d4 ?4 j8 a- ~把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主