Closed Bug 1284201 Opened 8 years ago Closed 7 years ago

Shared workers should support multiple content processes

Categories

(Core :: DOM: Workers, defect)

Product:
Core
Component:
DOM: Workers
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1207778
Tracking Flags:
Tracking Status
e10s - ---

People

(Reporter: gkrizsanits, Unassigned)

References

Details

(Whiteboard: [e10s-multi:M3]) 

Currently if two tabs from two separate content processes with same origin create a shared worker, they create separate instances instead of using a shared one.
Blocks: e10s-multi
Whiteboard: [e10s-multi:M1]
tracking-e10s: --- → ?
This is an e10s-multi only issue. With single content process e10s this problem can never happen.
Whiteboard: [e10s-multi:M1] → [e10s-multi:M3]
Blocks: e10s-multi-beta
baku, can you take a look here?
Flags: needinfo?(amarchesini)
How does this bug differ from bug 1207778?
Flags: needinfo?(gkrizsanits)
Initially bug 1207778 was just for ServiceWorker. Now it's about SharedWorkers. I mark this bug as duplicate of bug 1207778.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(amarchesini)
Resolution: --- → DUPLICATE
Flags: needinfo?(gkrizsanits)
You need to log in before you can comment on or make changes to this bug.