GWP-ASan: Refactor process sampling boost
Previously the caller to gwp_asan::EnableFor* would pass in various bools to indicate if sampling should be increased because this is an interesting process/release channel. This doesn't work well in a world where GWP-ASan hooks multiple allocators, instead have the caller simply indicate that process sampling should be boosted or not--not the specific conditions that led to increased process sampling. In doing so also change the previous ProcessSamplingBoost feature name/semantics to ProcessSamplingBoost2 since the boost is no longer cumulative. Bug: 956824 Change-Id: I70f646b15df5f002857c08bb104ffd881b5f2f3a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626031 Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Reviewed-by:Vitaly Buka <vitalybuka@chromium.org> Reviewed-by:
Greg Thompson <grt@chromium.org> Auto-Submit: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Cr-Commit-Position: refs/heads/master@{#662727}
Showing
Please register or sign in to comment