|
|
# Possible reasons:8 ~7 D; Q- o; f" s3 l) `, W
# The system is out of physical RAM or swap space
3 w5 n9 G. m" z2 Z* h! k4 X# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
$ S3 p' ?" i0 g/ v1 e! c! n* K# Possible solutions:
- o& L$ \. E7 O) s5 H* b# Reduce memory load on the system$ A+ B5 H" {- h! k9 n3 h4 v
# Increase physical memory or swap space5 m( a3 S- Z- u' u6 `1 D1 |* ^
# Check if swap backing store is full; O% |& |+ z3 X5 z
# Decrease Java heap size (-Xmx/-Xms)) w2 Y9 f) ^8 O4 N7 g4 o
# Decrease number of Java threads
4 B+ k) S8 C: N- ~: h, A9 J% Z# Decrease Java thread stack sizes (-Xss)
5 o7 d3 U1 C2 n- F. P: d) F. ?# Set larger code cache with -XX:ReservedCodeCacheSize=
8 U2 E0 u/ V4 n3 q# JVM is running with Zero Based Compressed Oops mode in which the Java heap is
- a7 t: q1 E( }8 l# placed in the first 32GB address space. The Java Heap base address is the
) M% F' ~3 U* k. a% B4 K# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress2 }9 _. J& ]# Y1 l# q2 S2 a; g7 j
# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
, C2 B& c# N! V8 R. `% ~把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主