Relax the overflow DCHECK in perf_profile_connector.cc. (#1779)

Summary: during `pem` startup, the transfer data method for various
source connectors can get starved i.e. not called at the correct
periodicity. This will cause the overflow `DCHECK` in the perf profiler
to fire. In this PR, we relax that condition.

Relevant Issues: #1683

Type of change: /kind bug fix

Test Plan: Existing tests.

---------

Signed-off-by: Pete Stevenson <[email protected]>

src/stirling/source_connectors/perf_profiler/perf_profile_connector.cc

@@ -368,7 +368,12 @@ void PerfProfileConnector::CheckProfilerState(const uint64_t num_stack_traces) {
   const uint64_t error_code =
       profiler_state_->GetValue(kErrorStatusIdx).ValueOr(kPerfProfilerStatusOk);
 
-  DCHECK_EQ(error_code, kPerfProfilerStatusOk);
+  // Set max overflow count non-zero because, during pem startup, the profiler transfer data
+  // method can get starved; i.e. we do expect a few overflow count errors during bringup.
+  constexpr int64_t max_overflow_error_count = 10;
+  constexpr int64_t max_map_read_error_count = 0;
+  DCHECK_LE(profiler_state_overflow_counter_.Value(), max_overflow_error_count);
+  DCHECK_LE(profiler_state_map_read_error_counter_.Value(), max_map_read_error_count);
 
   switch (error_code) {
     case kOverflowError: {