OpenJDK / amber / amber
changeset 46309:095f3eb41b22
8175900: Assertion too strict in G1CollectedHeap::new_mutator_alloc_region
Reviewed-by: simonis, tschatzl, kbarrett
Contributed-by: gunter.haug@sap.com
author | simonis |
---|---|
date | Mon, 27 Feb 2017 12:57:16 +0100 |
parents | 8b88f3db98b8 |
children | a2358af6cc81 385a8b027e7d |
files | hotspot/src/share/vm/gc/g1/g1CollectedHeap.cpp |
diffstat | 1 files changed, 0 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/hotspot/src/share/vm/gc/g1/g1CollectedHeap.cpp Mon Mar 06 09:24:47 2017 -0800 +++ b/hotspot/src/share/vm/gc/g1/g1CollectedHeap.cpp Mon Feb 27 12:57:16 2017 +0100 @@ -5269,8 +5269,6 @@ HeapRegion* G1CollectedHeap::new_mutator_alloc_region(size_t word_size, bool force) { assert_heap_locked_or_at_safepoint(true /* should_be_vm_thread */); - assert(!force || g1_policy()->can_expand_young_list(), - "if force is true we should be able to expand the young list"); bool should_allocate = g1_policy()->should_allocate_mutator_region(); if (force || should_allocate) { HeapRegion* new_alloc_region = new_region(word_size,