New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 674181 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug

Blocking:
issue 632361



Sign in to add a comment

NOSTATE_PREFETCH_FINISHED seen for offline namespace prerender requests

Project Member Reported by dougarnett@chromium.org, Dec 14 2016

Issue description

From Prerender.offline_FinalStatus UMA on Latest Canary (12/12/16), we are seeing high percentage of NOSTATE_PREFETCH_FINISHED for the "offline" namespace. 

Seems like a bug if NOSTATE_PREFETCH is intersecting with "offline" namespace prerenders.

Are they benign? It does not look like they are benign to us from prerender_contents->Destroy() here: https://cs.chromium.org/chromium/src/chrome/browser/prerender/prerender_message_filter.cc?rcl=1481631594&l=146 if that can happen before we are done with the WebContents.


PrerenderFinalStatus        PDF
TIMED_OUT                   00.28%
AUTH_NEEDED                 00.14%
RENDERER_CRASHED            00.14%
UNSUPPORTED_SCHEME          31.35%
CANCELLED                   45.86%
OPEN_URL                    00.14%
CREATING_AUDIO_STREAM       00.14%
NEW_NAVIGATION_ENTRY        01.93%
NOSTATE_PREFETCH_FINISHED   20.03%


 

Comment 1 by pasko@chromium.org, Dec 14 2016

Cc: pasko@chromium.org
Owner: droger@chromium.org
Status: Assigned (was: Untriaged)
It started appearing on December 8, which puts my suspicion on this December 7 change:
https://codereview.chromium.org/2537503002

Comment 2 by pasko@chromium.org, Dec 14 2016

Cc: mattcary@chromium.org
the fix would be easy to do in AddPrerender. It also leads me into thinking that we should not maintain prefetches_ for ORIGIN_OFFLINE. droger: WDYT?

Comment 3 by pasko@chromium.org, Dec 14 2016

Blocking: 632361

Comment 4 by droger@chromium.org, Dec 15 2016

This is indeed likely caused by the Finch experiment.
Why is this a bug though?
https://cs.chromium.org/chromium/src/chrome/browser/prerender/prerender_manager.cc?rcl=0&l=966

It seems like if we added an ORIGIN_OFFLINE check at the above line the problem might be fixed?

I think it's a bug because the experiment switches off offline rendering and so breaks offline.

Comment 6 by pasko@chromium.org, Dec 15 2016

Also, ORIGIN_EXTERNAL_REQUEST_FORCED_CELLULAR should be excluded. We won't be able to swap NoStatePrefetch in place of it easily, so there is no point of running this experiment.

Comment 7 by droger@chromium.org, Dec 15 2016

Status: Started (was: Assigned)
Re: why is this bug though?

The ORIGIN_OFFLINE use case needs a rendered WebContents to archive the page into MHTML for later use offline. This is used by new Chrome Downloads action. It is not a performance use case, it is a feature use case of the prerenderer. 

Comment 9 by droger@chromium.org, Dec 16 2016

CL ready:
https://codereview.chromium.org/2580753005/

Not sure when it'll land though, since I'll be OOO until January.

Comment 11 by pasko@chromium.org, Dec 16 2016

Status: Fixed (was: Started)

Sign in to add a comment