GitLab

ResourceDispatcherHost pushes pending load state of all frames to the UI
thread once every 250 milliseconds when there's a pending load.  This
happens even when the UI thread is blocked.  Apparently it's causing an
OOM when the UI thread is blocked.  Whatever is blocking the UI thread
is another issue entirely, but we shouldn't use unbounded memory in the
browser process.  This CL prevents load state updates from being sent
until the previous set was ACKed by the UI thread.

This is a reland of https://chromium-review.googlesource.com/978383,
which was reverted in https://chromium-review.googlesource.com/979674
for causing crashes after the RDH was shut down (Which should now be
fixed).

Bug: 824869
Change-Id: I84e594baefa6b246898e7df77abddaaa1a66fa0c
TBR: jam@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/980593
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#545836}