1260484 - Blob URLs need to work cross process

Status: RESOLVED DUPLICATE of bug 1279186

(Core :: DOM: Core & HTML, defect)

Comment 1

[Brad Lassey [:blassey] (use needinfo?)]

Kyle, Blake claims you have opinions.

Comment 2

[Andrea Marchesini [:baku]]

Is it about having multiple Content processes?

Comment 3

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Yeah, why does this matter for e10s?

Comment 4

[Brad Lassey [:blassey] (use needinfo?)]

We've band-aided the one issue we're aware of with a single content process (blob url favicons). This if for multiple content processes

Comment 5

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Ok, sure.  For multiple content processes ultimately we need to move the registry of blob URLs to the parent.

Comment 6

[Andrea Marchesini [:baku]]

Right, eventually we must do it. Just a quick reminder: our implementation of nsHostObjectProtocolHandler manages MediaStreams and Blobs. Only blob are multi-thread multi-process. What's the plan for MediaStream?

Comment 7

[Brad Lassey [:blassey] (use needinfo?)]

gcp just flagged for me that tab streams don't work across content processes, so that probably implies that we have work to do for MediaStream as well

Comment 8

[Maire Reavy [:mreavy]]

We talked about Tab capture in a multi-Content-Process environment some in our standup today and agreed we should open a bug.

Tab capture inherently must occur within a Content process, but the requesting code may live in a different Content process. For example, in a one-process-per-tab implementation, the capturing and consuming processes would always be different.

In this case, for multiple Content processes, we would need to pass capture requests through the Master process, as we do today for Camera access. The difference would be that the CamerasParent code would then pass down the request to the appropriate Content process, which would pass frames up to CamerasParent.  We might be able to optimize to avoid the round-trip when they're in the same process.  This is my understanding of how we're going to solve this problem; I'll transfer this summary to the new bug once it's opened.

MediaStreams are not multi-process - they are tied to a specific tab.  They're not transferrable, at least not yet.  This has been discussed in the Working Group some time ago, but there's no proposal currently to do so.

Comment 9

[Blake Kaplan (:mrbkap) (inactive)]

Andrea is working on this in bug 1279186, duping forward to that bug.