New issue
Advanced search Search tips

Issue 908672 link

Starred by 2 users
Status: Assigned
Owner:
s...@chromium.org
Cc:
pnoland@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

[Feed] mAppLifecycleListener.onClearAll(); called on first run

Project Member Reported by s...@chromium.org, Nov 27 
Install fresh Chrome w/ Feed enabled (--args="--enable-features=InterestFeedContentSuggestions"), and then sign in. The FeedAppLifecycle will be notified that we've signed in, and will subsequently ask the Feed to clear out all articles. This presumably no-ops, because there isn't any data to begin with, but it is also unnecessary disk access.

Comment 1 by s...@chromium.org, Nov 27

Cc: pnoland@chromium.org
Owner: s...@chromium.org
Hmm this actually seems to race with the foreground triggered refresh, though the clear seems to usually happen before the resulting refresh finishes. Too many races going on here.. Taking this back to think about.

Comment 2 by twelling...@chromium.org, Nov 27

Labels: zine-triaged
Status: Assigned (was: Untriaged)
We probably shouldn't be kicking up any of the Jardin machinery until first run has completed (e.g. we shouldn't schedule any fetches).

P3 seems like the right prioritization, though.
►

Sign in to add a comment