Closed Bug 853460 (WorkForTheWorkers) Opened 8 years ago Closed 1 year ago

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

Categories

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

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: Yoric, Unassigned)

References

(Depends on 5 open bugs, Blocks 1 open bug)

Details

(Keywords: meta, Whiteboard: [Snappy])

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.
Summary: [meta] Make Workers (more) useful for Snappy work → [meta] Make Workers (more) useful for chrome-priv code
- accessing preferences;
No, they are not. But we can build a threadsafe API on top of them.
Alias: WorkForTheWorkers
Whiteboard: [Snappy] → [Snappy][Async][Async Tooling]
Whiteboard: [Snappy][Async][Async Tooling] → [Snappy]
Depends on: 980689
Priority: -- → P3

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

Flags: needinfo?(bugmail)

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.

Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(bugmail)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.