|
|
# Possible reasons:
: h* h8 S# O; a, j4 |# The system is out of physical RAM or swap space
8 G$ l. Z% q1 l, n( \! y# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
7 z' ~5 K K0 V7 L3 y. V2 j4 t8 F# Possible solutions:5 `) ~$ T1 ]1 S e1 _
# Reduce memory load on the system5 j& M2 v; G4 d" q U) c. O
# Increase physical memory or swap space1 k2 i; i. a" P6 m
# Check if swap backing store is full2 J# S. L0 q- ^( a* f
# Decrease Java heap size (-Xmx/-Xms)
5 T: G9 f* h, z# l# Decrease number of Java threads1 @- {. G- d7 t8 I' W; ]2 R n
# Decrease Java thread stack sizes (-Xss)
3 M! d, O' o' e1 D6 O' J# Set larger code cache with -XX:ReservedCodeCacheSize=
1 |( _* A( T: V: w4 J6 c: T- p# JVM is running with Zero Based Compressed Oops mode in which the Java heap is' a6 @: {" I& ^' _
# placed in the first 32GB address space. The Java Heap base address is the
4 ]! a& V/ d7 A$ w: S2 L* X% ]# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress5 W A' c# [6 @6 a% z+ L% _
# to set the Java Heap base and to place the Java Heap above 32GB virtual address.* y' {/ }5 H3 R0 {, E Z
把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主