|
|
# Possible reasons:
. u, D6 ?/ ]$ \) o" t" p" @. v+ h# The system is out of physical RAM or swap space
% }, Q+ V3 j) O3 A' }; T* Q1 q# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap& s0 E5 g/ G! e% j( f4 P' ?
# Possible solutions:( ]+ i6 u, l# a
# Reduce memory load on the system
- X& k1 F* I# i5 g4 W! j# Increase physical memory or swap space
- i# u% o7 X) l+ q/ H# Check if swap backing store is full1 f# R0 J+ y. j# k+ m
# Decrease Java heap size (-Xmx/-Xms) |7 i. e2 s+ O1 I6 y4 {
# Decrease number of Java threads- s/ T! l; s1 k. t) G) a
# Decrease Java thread stack sizes (-Xss). G. a% p$ i" w5 z
# Set larger code cache with -XX:ReservedCodeCacheSize=
. c) D$ Y: t6 [/ K; x4 e# JVM is running with Zero Based Compressed Oops mode in which the Java heap is* @2 r# {- h Q: l0 `. o I
# placed in the first 32GB address space. The Java Heap base address is the
- }/ \. H+ P0 r8 {- u3 \' Y# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
. m, a8 @5 @2 ]! Z' T! t# r# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
- v4 a) h. d6 s5 W# p把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主