|
|
# Possible reasons:
! _8 \9 D/ k& b2 S# The system is out of physical RAM or swap space
8 B! z" W8 Q% g1 `8 {- a/ \' I) @# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap/ z. d. S' g6 u3 v/ a- C
# Possible solutions:! u( j9 R8 h- K# R1 D; b4 Z
# Reduce memory load on the system& x, v9 b6 h4 c" O8 S0 ^
# Increase physical memory or swap space
: w7 ~/ h: a" ~( B; s# Check if swap backing store is full9 ]- x9 a1 C2 [( ?3 G7 k
# Decrease Java heap size (-Xmx/-Xms)
4 q8 Q+ X* z9 S" r" i# x0 F# Decrease number of Java threads8 q4 r! l) O, W' A# I$ ]
# Decrease Java thread stack sizes (-Xss)# ]- ?- A- F. u' y% D4 K) `
# Set larger code cache with -XX:ReservedCodeCacheSize=
" Q, N( l" T- e3 U# JVM is running with Zero Based Compressed Oops mode in which the Java heap is1 ^ b5 }& Z% e2 i
# placed in the first 32GB address space. The Java Heap base address is the
3 q d. D1 |3 j! Y5 \5 A0 K# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
M a0 |' ]0 o5 P6 B" ]$ b# to set the Java Heap base and to place the Java Heap above 32GB virtual address.& B5 Y+ _9 j3 b# K/ I8 S
把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主