diff options
author | Peter Sollich <petersol@microsoft.com> | 2021-06-10 19:06:12 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-06-10 19:06:12 +0300 |
commit | 814f5cf88caa2755fcbf93ecf81e22efb0122a62 (patch) | |
tree | 0fa04baacc1f850bc016738b77e9f50f4c21d9c4 /src/coreclr/gc | |
parent | 7f260fbf08e135301b0c33bfba19afd01927c725 (diff) |
Disable STRESS_REGIONS (#53996)
There are several tests (most of them under GC\Scenarios\DoublinkList) that fail because STRESS_REGIONS pins arbitrary objects and thus keeps them alive, and thus these objects are not finalized.
Let's disable STRESS_REGIONS in the checked-in source code, but investigate whether there are any failures with STRESS_REGIONS that are real issues.
Diffstat (limited to 'src/coreclr/gc')
-rw-r--r-- | src/coreclr/gc/gcpriv.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/coreclr/gc/gcpriv.h b/src/coreclr/gc/gcpriv.h index b89a0043589..09bd97d1891 100644 --- a/src/coreclr/gc/gcpriv.h +++ b/src/coreclr/gc/gcpriv.h @@ -63,7 +63,7 @@ inline void FATAL_GC_ERROR() // + creates some pins on our own // + creates some ro segs // We can add more mechanisms here. -#define STRESS_REGIONS +//#define STRESS_REGIONS #endif //USE_REGIONS // FEATURE_STRUCTALIGN was added by Midori. In CLR we are not interested |