783827 - Rewrite remote audio backend

Status: RESOLVED WONTFIX

(Core :: Audio/Video: cubeb, defect, P2)

Description

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

+++ This bug was initially created as a clone of Bug #776069 +++

When the remote audio backend was implemented, some patches had been sitting in review for 6 months that would have let us implement something sane, using dedicated audio IPC channel(s).  Instead we had to layer hack upon hack upon hack, and the result is fragile.

I disabled this for now in bug 776069, which is terrible because it increases the OS attack surface from content processes.

Comment 1

[Matthew Gregan [:kinetik]]

I think this is a dupe of bug 770753, but this has the deps and CCs now.

Comment 3

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Indeed, sorry about that.

Comment 4

[Matthew Gregan [:kinetik]]

Renoming based on a discussion with dougt.  I'm not sure we should block on this--cjones may disagree; if so I defer to him.  I hadn't planned to work on it in the near future, but if we do end up blocking on it I can take it.

Per comment 0, we disabled the existing (buggy) audio remoting code, so we're no longer exposed to those bugs.  In exchange, we increase the attack surface of content<->chrome.  It's important to fix that, but the native audio API we're calling is a fairly small and restricted interface.

Comment 5

[Randell Jesup [:jesup] (needinfo me)]

Is this still relevant, or is it overtaken by events with the sandboxing work?

Comment 6

[Gian-Carlo Pascutto [:gcp]]

None of the code referred to seems to exist any more, so not much to rewrite.