HeyDennis
commented
3 years ago #
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 220200960 bytes for G1 virtual space
# Possible reasons:
# The system is out of physical RAM or swap space
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# JVM is running with Zero Based Compressed Oops mode in which the Java heap is
# placed in the first 32GB address space. The Java Heap base address is the
# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
# This output file may be truncated or incomplete.
#
# Out of Memory Error (os_windows.cpp:3466), pid=22272, tid=8384
#
# JRE version: Java(TM) SE Runtime Environment (16.0.1+9) (build 16.0.1+9-24)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (16.0.1+9-24, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
--------------- S U M M A R Y ------------
Command Line: C:\workspace\DMS\bin\..\lib\dms-0.2.7.jar
Host: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 8 cores, 15G, Windows 10 , 64 bit Build 19041 (10.0.19041.1023)
Time: Fri Oct 1 13:58:26 2021 Mitteleuropäische Sommerzeit elapsed time: 138.655982 seconds (0d 0h 2m 18s)
--------------- T H R E A D ---------------
Current thread (0x000001e5c55d5b60): VMThread "VM Thread" [stack: 0x0000000e92f00000,0x0000000e93000000] [id=8384]
Stack: [0x0000000e92f00000,0x0000000e93000000]
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
bei mir braucht der Windows-Befehlsprozessor stolze 1,6GB Arbeitsspeicher durchgehend.