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

Issue 717251 link

Starred by 1 user
Status: Fixed
Owner:
fgor...@chromium.org
Closed: May 2017
Cc:
dewittj@chromium.org
█ dim...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Background Task Scheduler should be able to initialize the native library

Project Member Reported by dewittj@chromium.org, May 1 2017 
As described in Issue 704990, we shouldn't have to write native initialization code in individual tasks, it should be handled by BackgroundTaskScheduler's API somehow.

Comment 1 by dim...@chromium.org, May 3 2017

Status: Assigned (was: Untriaged)

Comment 2 by fgor...@chromium.org, May 31 2017

Status: Fixed (was: Assigned)
This has been taken care of here:

[Android] Native initialization task for BackgroundTaskScheduler

Provides an abstract class implementing BackgroundTask with capability
to ensure that native portion of Chrome is initialized.

BUG= 710630 
R=nyquist@chromium.org

Review-Url: https://codereview.chromium.org/2825783003
Cr-Commit-Position: refs/heads/master@{#474385}
Committed: https://chromium.googlesource.com/chromium/src/+/acd0e4ec71292ce486b7a5d9ca5ecece6712bfa3
►

Sign in to add a comment