|
|
# Possible reasons:
6 N/ @* c! c5 r- u% D8 j/ |1 @# The system is out of physical RAM or swap space% ~! `- y% W: d) g
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap! ?- P. M! A9 n: P' y
# Possible solutions:! E7 b6 U! e- R, d8 l5 ?
# Reduce memory load on the system- V) u/ V5 @( u1 J
# Increase physical memory or swap space$ Q3 g5 `/ u; h7 s8 x F% ^
# Check if swap backing store is full& r3 _" \7 C6 x B" T
# Decrease Java heap size (-Xmx/-Xms)- R4 z- z2 `5 B# M6 u
# Decrease number of Java threads# b- s6 I- Z3 u6 b# f% H$ I
# Decrease Java thread stack sizes (-Xss)& B2 G' R, L* Z0 g- |; L% _
# Set larger code cache with -XX:ReservedCodeCacheSize=
/ ?! H% G! m( V7 J! Y2 z8 \# JVM is running with Zero Based Compressed Oops mode in which the Java heap is& T0 M( R* z: C) ` J* k% {6 S! T2 R
# placed in the first 32GB address space. The Java Heap base address is the
' ^8 c3 X) I5 L: f# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
9 B, a6 t( y, |; C: A8 F# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
; t4 d3 `; m; W8 h. r( P把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主