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

Issue 682761 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Track down the ~5min timeout for prerenderer(maybe?)

Project Member Reported by romax@chromium.org, Jan 19 2017

Issue description

From a test harness run with StartImmediateSchedule() call which has 8 minute timeout, I'm seeing some LOADING_FAILED_NO_NEXT logs happening after ~5 minutes. So if there's a timeout of 5mins on Prerenderer probably we should reduce our timeout from 8 minutes to 5.
Here's a snippet of log:

01-18 21:16:43.396: EvalProgress@@@@@@ | http://lista.mercadolivre.com.br/drill#D[A:drill] is saved with result: SUCCESS. (18/100)
01-18 21:21:43.908: OPNative | Background save attempt for async_loading:6745558171835941097 - LOADING_FAILED_NO_NEXT
01-18 21:26:44.497: OPNative | Background save attempt for async_loading:7778472014508007078 - LOADING_FAILED_NO_NEXT
01-18 21:27:36.946: OPNative | http://www.olx.co.id/elektronik-gadget/handphone/samsung is saved at async_loading with id 6745558171835941097
01-18 21:27:36.952: OPNative | Background save attempt for async_loading:6745558171835941097 - SAVED
01-18 21:27:36.987: EvalProgress@@@@@@ | http://olx.co.id/elektronik-gadget/handphone/samsung/ is saved with result: SUCCESS. (19/100)
01-18 21:32:37.430: OPNative | Background save attempt for async_loading:7778472014508007078 - LOADING_FAILED_NO_NEXT
01-18 21:37:37.896: OPNative | Background save attempt for async_loading:7778472014508007078 - LOADING_FAILED_NO_NEXT
01-18 21:37:37.898: OPNative | Background save request removed async_loading:7778472014508007078 - RETRY_COUNT_EXCEEDED

Full log attached.
 
without_change_2gpoor.txt
68.2 KB View Download
Project Member

Comment 2 by bugdroid1@chromium.org, Jan 24 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7b45a25edbef4bb26bf1d82c71aa1bca36b89a47

commit 7b45a25edbef4bb26bf1d82c71aa1bca36b89a47
Author: petewil <petewil@chromium.org>
Date: Tue Jan 24 23:44:00 2017

Reduce the "immediate" timeout to 4 min 50 sec to match prerenderer.

The prerenderer has a built in 5 minute timeout, and will not go past
5 minutes anyway, so set our timeout for an immediate fetch to 4 min 50 sec
so that we don't exceed the prerenderer timeout.

BUG= 682761 

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

[modify] https://crrev.com/7b45a25edbef4bb26bf1d82c71aa1bca36b89a47/components/offline_pages/core/background/offliner_policy.h

Status: Fixed (was: Assigned)

Sign in to add a comment