Address large number of ERR_IPC_WITH_NO_RELEVANT_LOADs |
||
Issue descriptionWe see a large number of ERR_IPC_WITH_NO_RELEVANT_LOADs. It appears these may be due to prerender, at least in part, as we don't create a PageLoadTracker for prerenders but the render process will send metrics. Since we intend to track prerenders, the simplest fix for now is to create a PageLoadTracker but immediately stop tracking metrics on it. Eventually, we can update this logic to enable tracking of metrics for prerenders that get used. See bug 648338 for more on this.
,
Sep 22 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e8b60aa78b10f60af6d3f879385f5db1e8ac427a commit e8b60aa78b10f60af6d3f879385f5db1e8ac427a Author: bmcquade <bmcquade@chromium.org> Date: Thu Sep 22 18:18:19 2016 Instantiate PageLoadTrackers for prerenders This gets us closer to adding support for tracking prerenders ( bug 648338 ), and addresses bug 648341 where an internal error is logged every time a prerender sends metrics data from the render process to the browser process. BUG= 648341 Review-Url: https://codereview.chromium.org/2354703002 Cr-Commit-Position: refs/heads/master@{#420398} [modify] https://crrev.com/e8b60aa78b10f60af6d3f879385f5db1e8ac427a/chrome/browser/page_load_metrics/metrics_web_contents_observer.cc [modify] https://crrev.com/e8b60aa78b10f60af6d3f879385f5db1e8ac427a/chrome/browser/page_load_metrics/metrics_web_contents_observer_unittest.cc
,
Sep 25 2016
Data coming back from canary suggests that this issue is essentially addressed by the prerender change. The volume of ERR_IPC_WITH_NO_RELEVANT_LOADs is now 1% that of the number of NavigationToFirstContentfulPaints, well within reasonable levels. |
||
►
Sign in to add a comment |
||
Comment 1 by bmcquade@chromium.org
, Sep 20 2016