Increase buffer sizes in TCMalloc tests.

We are nearing these limits, and the tests are becoming flakey

PiperOrigin-RevId: 831376536
Change-Id: I2ed89d4269088e52f0694f2775421a67875874a0

Author: TCMalloc Team

tcmalloc/testing/reclaim_test.cc

@@ -93,11 +93,11 @@ TEST(ReclaimTest, ReclaimWorks) {
   // Allocate strings, so that they don't need to be reallocated below, and so
   // don't perturb what we're trying to measure.
   //
-  // As of December 2024, this size, plus the null terminator on the
+  // As of November 2025, this size, plus the null terminator on the
   // std::string, is well outside of the size classes used by TCMalloc, so a
   // resize will not perturb the per-CPU cache.
-  before.reserve(1 << 20);
-  after.reserve(1 << 20);
+  before.reserve(1 << 21);
+  after.reserve(1 << 21);
 
   // Generate some traffic to fill up caches.
   const int kThreads = 10;

tcmalloc/testing/testutil.cc

@@ -83,7 +83,7 @@ int VirtualCpu::TestSynchronize() { return ScopedFakeCpuId::test_vcpu_; }
 
 std::string GetStatsInPbTxt() {
   // When huge page telemetry is enabled, the output can become very large.
-  const int buffer_length = 3 << 20;
+  const int buffer_length = 3 << 21;
   std::string buf;
   if (&MallocExtension_Internal_GetStatsInPbtxt == nullptr) {
     return buf;