Reland of "[tracing] Add browser-side tests for memory dumps."

This is identical to https://crrev.com/1290103004. Once
https://crrev.com/1289793007 lands the tests should no longer be flaky.

Original description below:

The original CL (https://crrev.com/1295753002) got reverted due to test
flakiness. This was because of the memory dump manager performing a
periodic memory dump. If the test completed before such a dump would be
done, it would pass, but when a periodic dump happened during the test,
OnMemoryDump would be called too often. The solution is to disable
periodic memory dumps in tests. This needs to be done via TraceConfig in
the long term, for now this is a workaround.

BUG=518823, 522009, 522165
TBR=dsinclair@chromium.org

Review URL: https://codereview.chromium.org/1308443002

Cr-Commit-Position: refs/heads/master@{#345076}


CrOS-Libchrome-Original-Commit: 6cbb92a6de7198fbf824e8b50c10ae115d789e1a
2 files changed
tree: 416b6391093525130420dadbcf6f49a4e04357db
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/