Closed Bug 1187441 Opened 9 years ago Closed 8 years ago

Use separate content processes for e10s browsing and thumbnail generation


(Core :: DOM: Content Processes, defect, P3)




Tracking Status
e10s + ---
firefox42 --- affected


(Reporter: mconley, Assigned: blassey)


(Blocks 1 open bug)



(1 file)

With e10s enabled and dom.ipc.processCount = 1, the content process is shared between general browsing and the thumbnail generation process.

The thumbnail generation process is going to periodically load pages in the background, render them, and generate thumbnails from them. It might be a nice perf win to take that work out of the content process that the user is browsing with.

We'd probably want to distinguish between this process and general content processes somehow with Telemetry, etc.
Here's a patch to do this. It's probably reasonable to have a discussion as to whether we want to do this or not.
Assignee: nobody → blassey.bugs
Attachment #8640468 - Flags: review?(wmccloskey)
Comment on attachment 8640468 [details] [diff] [review]

Review of attachment 8640468 [details] [diff] [review]:

I don't think we should do this for thumbnailing. If I have two content processes running, I don't want to waste one of them for just thumbnails. I think I'd get much more benefit if my tabs were split between them, with thumbnailing in one of them.

However, I think it might make sense to do a more general version of this. I'd really like to see two attributes on the frame element, both strings:
- processTribe
- processFamily

Two frames that are in different processTribes can never run in the same process. Two frames that are in the same processFamily must always live in the same process. (Please suggest better names.)
Attachment #8640468 - Flags: review?(wmccloskey) → review-
Priority: -- → P3
Blocks: 1249880
I agree with Bill that we shouldn't do this particular thing. Process tribes are something to design later, not worth leaving a bug open.
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.