|
|
# Possible reasons:1 W1 d O: T! s9 l" G; q. l
# The system is out of physical RAM or swap space; s/ h' W3 t8 T* D, t
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
7 [& `" C8 E5 Z! q6 ^# Y" M& _# Possible solutions:
* H. y6 ?" c3 I! A2 A5 I# Reduce memory load on the system
z0 D: ~7 k: S# Increase physical memory or swap space2 Y8 h. t4 a, @ m0 L
# Check if swap backing store is full5 Q; g) d0 T8 N+ N- H3 m
# Decrease Java heap size (-Xmx/-Xms)0 ]2 R% z( r0 I0 |7 J
# Decrease number of Java threads
1 P) w2 Z/ A) U/ z' r! @' M# Decrease Java thread stack sizes (-Xss)
% Y1 Y, ~ G4 B9 c# Set larger code cache with -XX:ReservedCodeCacheSize=
: W9 s1 A; g: `' l7 Q3 R5 N# JVM is running with Zero Based Compressed Oops mode in which the Java heap is$ h" i7 q. E! D' a9 o8 }1 `
# placed in the first 32GB address space. The Java Heap base address is the
! f5 d$ F- @7 g2 Y4 H' Q# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress6 F. g! Z( h N8 j( B E7 U) O# w
# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
- d6 t3 y2 R) O把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主