Revert of Do V8 GC ASAP if system memory is pressured (patchset #13 id:240001 of https://codereview.chromium.org/1749073002/ )

Reason for revert:
Crash in CallOnForegroundThread
BUG=609056

Original issue's description:
> Do V8 GC ASAP if system memory is pressured
>
> Currently after receiving memory pressure notification, Chrome posts
> asynchronous task to renderer main thread to trigger V8 GC. If renderer
> main thread is busy, purging memory task will be postponed running,
> which increases OOM risk.
>
> The CL can send memory pressure notification to renderer main thread
> synchronously and trigger V8 GC while V8 is in the middle of executing
> JavaScript.
>
> The CL depends on CL 1813963002
>
> BUG=590975
>
> Committed: https://crrev.com/f80422e52658fd87d4159bfeeddd703bae1d4180
> Cr-Commit-Position: refs/heads/master@{#391167}

TBR=esprehn@chromium.org,jochen@chromium.org,kinuko@chromium.org,mark@chromium.org,rmcilroy@chromium.org,ulan@chromium.org,hong.zheng@intel.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=590975

Review-Url: https://codereview.chromium.org/1953483002
Cr-Commit-Position: refs/heads/master@{#391636}


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