MemoryInfra: temporary fix for stack overflow when creating memory dump

When there are too many providers registered, calling
SetupNextMemoryDump causes stack overflow. This happens very frequently
when OOPIF is turned on. As a temporary fix for this issue, just loop
around all the skipped dump providers. This should reduce majority of
the crashes since there are very few dump providers whitelisted for
background and summary modes.

BUG=797784

Change-Id: If635978ad11ee624f09f3e22fccea0ce1252b20d
Reviewed-on: https://chromium-review.googlesource.com/849619
Reviewed-by: Ɓukasz Anforowicz <lukasza@chromium.org>
Reviewed-by: Hector Dearman <hjd@chromium.org>
Reviewed-by: Primiano Tucci <primiano@chromium.org>
Commit-Queue: Siddhartha S <ssid@chromium.org>
Cr-Commit-Position: refs/heads/master@{#527725}

CrOS-Libchrome-Original-Commit: 73f5ffc6bb3150782fdd738a091cb9eeb37dcf03
1 file changed
tree: 64cba859da74c2e0007fe7b9ccbd49f9e71b613b
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/