Open
Bug 1054841
(shared-array-buffer)
Opened 10 years ago
Updated 1 year ago
[meta] Shared memory for web workers
Categories
(Core :: JavaScript Engine, defect, P3)
Core
JavaScript Engine
Tracking
()
NEW
mozilla55
People
(Reporter: lth, Unassigned)
References
(Depends on 11 open bugs, Blocks 1 open bug)
Details
(Keywords: dev-doc-complete, meta, Whiteboard: [games:p1])
This is a meta-bug for JS engine tasks related to providing shared memory for web workers: - SharedArrayBuffer issues - SharedTypedArray type hierarchy - Atomics and locks, including JIT support
Reporter | ||
Comment 1•10 years ago
|
||
Spec: https://docs.google.com/document/d/1NDGA_gZJ7M7w1Bh8S0AoDyEqwDdRh4uSoTPSNn77PFk/edit?usp=sharing Patch queue: https://github.com/lars-t-hansen/atomics-queue
Reporter | ||
Comment 2•10 years ago
|
||
Implementation matrix: https://docs.google.com/spreadsheets/d/1PFa3aDxY6mffT8uoflCaFitX9lKj_Y4_aZwtMApIRiI/edit?usp=sharing
Reporter | ||
Comment 3•10 years ago
|
||
The "making sausage" document (background discussion, early drafts, opinions, options): https://docs.google.com/document/d/1qGXAzk7Qq0z87fWrgpS6Ww-ISAsLRxQhLRc0GmQlunU/edit?usp=sharing
Reporter | ||
Updated•10 years ago
|
Depends on: %TypedArray%
Updated•9 years ago
|
Keywords: dev-doc-needed
Whiteboard: [games:p1]
Reporter | ||
Updated•7 years ago
|
Reporter | ||
Updated•7 years ago
|
Alias: shared-array-buffer
Comment 4•7 years ago
|
||
https://hacks.mozilla.org/2016/05/a-taste-of-javascripts-new-parallel-primitives/ https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Atomics
Keywords: dev-doc-needed → dev-doc-complete
Reporter | ||
Comment 5•7 years ago
|
||
SAB shipped on-by-default in Firefox 55. I'm going to keep this bug open because of the remaining blockers, some of which we'll need to get to before long (notably MessageError and the fine points of structured cloning).
Reporter | ||
Comment 6•7 years ago
|
||
This bug is now just tracking mop-up work, so P3 and unassigning self. The mop-up work items should be managed individually.
Assignee: lhansen → nobody
Priority: -- → P3
Comment 7•7 years ago
|
||
Wouldn't it be better to create a new meta bug for the follow-up work so we can mark this one as fixed?
status-firefox55:
--- → fixed
status-firefox56:
--- → fixed
status-firefox57:
--- → fixed
Target Milestone: --- → mozilla55
Updated•3 years ago
|
Blocks: sm-runtime
Updated•1 year ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•