From: Hyeongseok Oh <hseok82.oh@samasung.com>
Date: Thu, 20 Oct 2016 10:23:53 +0000 (+0900)
Subject: GC for large object allocation when fail to get new segment
X-Git-Tag: accepted/tizen/base/20180629.140029~3284^2
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=6f09643f0a8d550eaa6e4f5ad131955b6eefdab9;p=platform%2Fupstream%2Fcoreclr.git

GC for large object allocation when fail to get new segment

Delete unnecessary line
---

diff --git a/src/gc/gc.cpp b/src/gc/gc.cpp
index 6cea472..028a9f8 100644
--- a/src/gc/gc.cpp
+++ b/src/gc/gc.cpp
@@ -14785,6 +14785,9 @@ int gc_heap::generation_to_condemn (int n_initial,
         dprintf (GTC_LOG, ("h%d: alloc full - BLOCK", heap_number));
         n = max_generation;
         *blocking_collection_p = TRUE;
+        if ((local_settings->reason == reason_oos_loh) ||
+            (local_settings->reason == reason_alloc_loh))
+            evaluate_elevation = FALSE;
 
         local_condemn_reasons->set_condition (gen_before_oom);
     }
@@ -16499,7 +16502,7 @@ int gc_heap::garbage_collect (int n)
         if ((settings.condemned_generation == max_generation) &&
             (recursive_gc_sync::background_running_p()))
         {
-            //TODO BACKGROUND_GC If we just wait for the end of gc, it won't woork
+            //TODO BACKGROUND_GC If we just wait for the end of gc, it won't work
             // because we have to collect 0 and 1 properly
             // in particular, the allocation contexts are gone.
             // For now, it is simpler to collect max_generation-1