|
|
# Possible reasons:
0 L/ p# P4 m; M6 U5 S1 ]) y# The system is out of physical RAM or swap space
* \/ g- C" h4 Y5 Q8 u# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap( Z2 v% x0 p) F& D4 s T" [
# Possible solutions:
3 O3 b: _2 l. {$ C+ ?. F# Reduce memory load on the system9 ~1 u7 o2 p. S* {; z1 S0 N( p
# Increase physical memory or swap space
. g0 |9 T) g% E& K6 k# Check if swap backing store is full
- Q% U- k% B% m+ |% D; H' H# Decrease Java heap size (-Xmx/-Xms)% n2 ^ L/ z5 t4 e) O3 q) D
# Decrease number of Java threads' \' J6 C8 y8 w2 \, F2 J
# Decrease Java thread stack sizes (-Xss)2 U# |) Z0 z% p3 Q/ g8 r6 y! f
# Set larger code cache with -XX:ReservedCodeCacheSize=
+ X$ ~# b6 r7 I+ D# \ Z, c' j5 E# JVM is running with Zero Based Compressed Oops mode in which the Java heap is- Y) n# ?2 w( u& @4 H
# placed in the first 32GB address space. The Java Heap base address is the" g% b b) q# ?" x) J+ j) f& [
# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress5 G @+ P7 F% W9 V4 m
# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
5 K- a- y- h' A( r3 j$ u" D把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主