Open Bug 1763651 Opened 4 years ago Updated 1 month ago

MSE in workers

Categories

(Core :: Audio/Video: Playback, enhancement, P2)

enhancement

Tracking

()

People

(Reporter: jrmuizel, Assigned: aosmond)

References

(Blocks 2 open bugs)

Details

(Keywords: parity-chrome, parity-safari, Whiteboard: [platform-feature])

User Story

https://mozilla-hub.atlassian.net/browse/FFXP-1846
platform-scheduled:2026-03-31
webcompat-risk:high
Blocks: twitch
Blocks: MSE

I've started some prototyping related to this. The patches on this branch should do the plumbing to expose MediaSource on worker threads and such. What needs to happen now is to plumb this properly into HTMLMediaElement's selection/attach/detach logic. I hoping to get a chance to look at this in the next week (but it is best effort in my free time :)).

https://github.com/aosmond/gecko/tree/ao_mse_worker

Whiteboard: webcompat:risk-moderate

This should really be high risk, or you could roll it into the general web compat bug lists. We're actively working on this now.

Assignee: nobody → aosmond
Severity: -- → S2
Flags: needinfo?(twisniewski)
User Story: (updated)

Thanks for the heads-up, Jim. I agree. I'll update this bug for now, and we can re-organize things later if we feel it's worthwhile.

Flags: needinfo?(twisniewski)
Whiteboard: webcompat:risk-moderate → webcompat:risk-high
User Story: (updated)
Severity: S2 → S3
Priority: -- → P2
User Story: (updated)
Whiteboard: webcompat:risk-high → [platform-feature][webcompat:risk-high]

Similar to twich, kick.com is also slower compared to Chrome, and it looks like this is the culprit too. Channel switching there (while in a channel, clicking to another channel on the left sidebar to switch) is pretty slow in Firefox compared to Chrome, ~2.28s in Firefox vs ~868ms in Chrome.

It looks like kick uses Amazon IVS Player SDK, which means that this is probably issue for any website that uses Amazon IVS Player. The sdk has a gate called isSupportedInWorker for checking if it's supported in worker and falls back to sendRPC (with postMessage) if it's not supported.

User Story: (updated)
Whiteboard: [platform-feature][webcompat:risk-high] → [platform-feature]
You need to log in before you can comment on or make changes to this bug.