853460 - (WorkForTheWorkers) [meta] Make Workers (more) useful for chrome-priv code

Status: RESOLVED WORKSFORME

(Core :: DOM: Workers, defect, P3)

Description

[David Teller [:Yoric] - still alive but not very active]

For the moment, Chrome Workers lack many features that would be useful to make Snappy refactorings.

e.g.:
- accessing the database;
- accessing add-on data;
- accessing session restore data;
- ...

Opening this bug to keep track of efforts made to improve this situation.

Comment 1

[David Teller [:Yoric] - still alive but not very active]

- accessing preferences;

Comment 2

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Preferences are not threadsafe.

Comment 3

[David Teller [:Yoric] - still alive but not very active]

No, they are not. But we can build a threadsafe API on top of them.

Comment 4

[Jens Stutte [:jstutte]]

:asuth, is this meta-bug still meaningful (the last "real" change dates 6 years ago).

Comment 5

[Andrew Sutherland [:asuth] (he/him)]

From this component's perspective, I think we can indeed call this meta bug concluded. Most of the remaining open bugs are aspirational bugs in other components or have been rendered moot by platform changes. That said, it could make sense to move this bug to toolkit/browser, but I think :Yoric is no longer working in this area of the code-base and I think in general we've tried to limit the use of ChromeWorkers for system-level components post-Firefox OS where the memory usage was noted to be a problem.