GWP-ASan: Update default sampling frequency

My current experiment indicates this is the best default parameter to
use in terms of performance versus crashes.

Bug: 896019
Change-Id: I59028eba3bc994970d49b031e547a078f9702ba0
Reviewed-on: https://chromium-review.googlesource.com/c/1389020Reviewed-by: Vitaly Buka <vitalybuka@chromium.org>
Commit-Queue: Vitaly Buka <vitalybuka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#618659}

components/gwp_asan/client/gwp_asan.cc

@@ -29,7 +29,7 @@ const base::FeatureParam<int> kMaxAllocationsParam{&kGwpAsan, "MaxAllocations",
 const base::FeatureParam<int> kTotalPagesParam{&kGwpAsan, "TotalPages", 128};
 
 const base::FeatureParam<int> kAllocationSamplingParam{
-    &kGwpAsan, "AllocationSamplingFrequency", 128};
+    &kGwpAsan, "AllocationSamplingFrequency", 1000};
 
 const base::FeatureParam<double> kProcessSamplingParam{
     &kGwpAsan, "ProcessSamplingProbability", 1.0};