GitLab

IsPartitionAllocPCScanBrowserOnlyEnabled used to return false
unconditionally on 32-bit architectures. This led to necessity to set up
different populations in Omaha for each architecture, which is error
prone. After changing this, the responsibility for checking the bitness
falls now on EnablePCScanForMallocPartitionsInBrowserProcessIfNeeded.

The caveat is that the population with PartitionAllocPCScanBrowserOnly
turned on on 32-bit systems will now have to be ignored. This is ok
because we get enough data on Windows.

Make a similar change to EnablePCScanForMallocPartitionsIfNeeded for
consistency, and overall clean up the code to look more symmetrical,
while at it.

Bug: 11297512
Change-Id: Ia4eccdbea149389e3a192c5b618cb938a701c388
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2597240Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Will Harris <wfh@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Anton Bikineev <bikineev@chromium.org>
Commit-Queue: Bartek Nowierski <bartekn@chromium.org>
Auto-Submit: Bartek Nowierski <bartekn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#841732}