Community
Participate
Working Groups
Created attachment 278413 [details] Report files generated by java I checked out the eclipse-project itself (https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/). While compiling it, eclipse crashes every time. Here is my eclipse.ini: ----------------------------------------- ----------------------------------------- -startup plugins/org.eclipse.equinox.launcher_1.5.300.v20190213-1655.jar --launcher.library C:/Users/alexa/.p2/pool/plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.1000.v20190125-2016 -product org.eclipse.epp.package.jee.product -showsplash org.eclipse.epp.package.common --launcher.defaultAction openFile --launcher.appendVmargs -vm D:\Programme\Java\jdk1.8.0_212\bin\ -vmargs -Duser.name=Alexander Guril -Declipse.p2.max.threads=10 -Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest -Doomph.redirection.index.redirection=index:/->http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/ -javaagent:D:\Programme\Eclipse IDE for Java EE\jee-2018-12\eclipse\lombok.jar -Dosgi.requiredJavaVersion=1.8 -Dosgi.instance.area.default=@user.home/eclipse-workspace -XX:+UseG1GC -XX:+UseStringDeduplication -XX:+HeapDumpOnOutOfMemoryError --add-modules=ALL-SYSTEM -Dosgi.requiredJavaVersion=1.8 -Dosgi.dataAreaRequiresExplicitInit=true -Xms1m -Xmx3G --add-modules=ALL-SYSTEM ----------------------------------------- ----------------------------------------- I use Eclipse IDE for Enterprise Java Developers. Version: 2019-03 (4.11.0) Build id: 20190314-1200. It is also reproducible in Version 4.12. I use the latest Version of Java JDK 8: java version "1.8.0_212" Java(TM) SE Runtime Environment (build 1.8.0_212-b10) Java HotSpot(TM) 64-Bit Server VM (build 25.212-b10, mixed mode) My OS-Version: Windows 10 Education Version 1803 (Build 17134.706)
Have you tried to follow proposals below, written in the error dump? # There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (mmap) failed to map 5242880 bytes for Failed to commit area from 0x0000000716700000 to 0x0000000716c00000 of length 5242880. # 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:3371), pid=6532, tid=0x00000000000052c8 # # JRE version: Java(TM) SE Runtime Environment (8.0_212-b10) (build 1.8.0_212-b10) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.212-b10 mixed mode windows-amd64 compressed oops)
@Andrey Loskutov Yes, that was my first idea. First, I followed the instructions in the error dump. That did not work. As a second step, I searched the internet for solutions. They did not help me either.
Which party could *possibly* fix this issue? I see no proof that sufficient physical memory is available, so the error could require to be fixed by the user. Perhaps the JVM fails to allocate memory for some other reason than reported? Would be a JVM bug then. Perhaps, org.eclipse.core.internal.resources.SaveManager is putting to much pressure on memory? (I have no detailed theory, just guessing a long shot). I don't see JDT anywhere in the picture. => Moving the bug to Platform/Resources for good measure.
