The bug is filed to understand better the hotspot implementation of System.gc () with G1 and CMS with and without -XX:+ExplicitGCInvokesConcurrent. Thus determine if this is a test bug or a bug in the …

These tests specify -XX:+UseG1GC with -XX:ParallelGCThreads=0 which is an illegal combination since JDK-8059527 was fixed. hotspot/test/gc/8000311/Test8000311.java …

With UseG1GC, specifying -XX:ParallelGCThreads=0 is no longer allowed. Previously, with -XX:ParallelGCThreads=0, G1 would execute some tasks using serial code executed by the VM thread.

Oracle Java is the #1 programming language and development platform. It reduces costs, shortens development timeframes, drives innovation, and improves application services.

We have taken the decision to remove the +UseG1GC options from under the -XX:+UseExperimentalVMOptions flag.

Running on my machine with various options produces the below: Options: -Xmx8G -verbose:gc -XX:+UseConcMarkSweepGC [GC (Allocation Failure) 4197K->489K (253440K), 0.0012620 secs] …

To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /tmp/8/hs_err_pid12479.log

How reproducable is the problem? Run a java program which keeps allocating memory with following options. -XX:+UseG1GC -XX:G1ConfidencePercent=200 system configuration …

Welcome to the Java.com Help Center where we describe solutions for issues you might encounter when downloading and using Java on your computer. We track the most frequently reported issues …

With the classic concurrent mark sweep the memory is reclaimed correctly, but not with G1. STEPS TO FOLLOW TO REPRODUCE THE PROBLEM : Use the Java code below to generate and intern …