Reland: Call blink::WebMemoryCoordinator::OnPurgeMemory in RenderThreadImpl::ReleaseFreeMemory - 2
This reverts commit cdd97e24. After perf-bot reported a regression in timeToFirstMeaningfulPaint, timeToFirstContentfulPaint, and timeToFirstPaint on android nexus5, the original CL was reverted. However, the regression looks reasonable because ReleaseMemory could be called before FCP and FMP came on low-end devices if the website needs to use much memory. I guess that the regression caused because the test website(edition.cnn.com) was consuming too much memory on the mobile device. Bug: 850977, 851868 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: Icc8e5f24c114947fe8d186f699d0457ea82b7416 Reviewed-on: https://chromium-review.googlesource.com/1096921Reviewed-by:Kentaro Hara <haraken@chromium.org> Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com> Cr-Commit-Position: refs/heads/master@{#568023}
Showing
Please register or sign in to comment