New issue
Advanced search Search tips

Issue 740773 link

Starred by 2 users
Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Task

Blocking:
issue 675631



Sign in to add a comment

WebDataService (etc.) should use sequenced task runners, not single-threaded

Project Member Reported by pkasting@chromium.org, Jul 11 2017 
The WebDataService code passes around a "db_thread" object extensively to represent the database thread.  This has been replaced by a single-threaded task runner; it should probably be further cleaned up to be a sequenced task runner.  It could perhaps be even further cleaned up to not be the same task runner in all subsidiary objects.

Comment 1 by pkasting@chromium.org, Jul 11 2017

Blocking: 675631

Comment 2 by pkasting@chromium.org, Jul 11 2017

Summary: WebDataService (etc.) should use sequenced task runners, not single-threaded (was: WebDatabase should use sequenced task runners, not single-threaded)

Comment 3 by pkasting@chromium.org, Jul 11 2017

Description: Show this description
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 11

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by pkasting@chromium.org, Jul 11

Status: Available (was: Untriaged)
►

Sign in to add a comment