DOMStorage: Use a new task runner for domstorage service |
|
Issue descriptionCurrently DOMStorage mojo service in the browser uses a sequenced task runner on the IO thread. Have it grab a new one instead, not tied to a thread.
,
Jan 9
Not sure what the reasoning behind this change is? What benefits are we expecting to get out of this?
,
Jan 9
Asking because especially during shutdown there are a bunch of subtleties around what tasks run on which task runners, and if that lets us flush data to disk or not. It might very well be safe now to move this to a separate sequence/thread (although it would add more thread hops in some cases), but at least when the code was written it very intentionally used the IO thread and not some random thread pool (well, okay, when the code was written we didn't have the infra to use a random thread pool thread or something like that).
,
Jan 9
It's nice to be a good service that doesn't live on the IO thread.
,
Jan 9
Fair enough. |
|
►
Sign in to add a comment |
|
Comment 1 by dmu...@chromium.org
, Jan 9