Closed Bug 1376894 Opened 7 years ago Closed 3 years ago

Support a special attribute on <xul:browser>'s that cause the next page load to use a preallocated process

Categories

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

Product:
Core
Component:
DOM: Content Processes
Type:
enhancement

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: mconley, Unassigned)

References

Details

(Whiteboard: e10s-multi:+)

We want the preloaded about:newtab page to only use a preallocated process once it has navigated somewhere (until then, it should use a pre-existing content process). gabor suggested that we decorate the preloaded about:newtab page with a special attribute, and then have nsFrameLoader/ContentParent do some sleight-of-hand to switch the process that the content is loading in to the next preallocated content process (if a preallocated content process is available).
Blocks: 1376895
Hey gabor, can we just assign this to you?
Flags: needinfo?(gkrizsanits)
Assignee: nobody → gkrizsanits
Flags: needinfo?(gkrizsanits)
Blocks: 1381804
Priority: -- → P3
Summary: Support a special attribute on <xul:browser>'s that cause the next page load to use the preallocated process → Support a special attribute on <xul:browser>'s that cause the next page load to use a preallocated process
Whiteboard: e10s-multi:+

The bug assignee didn't login in Bugzilla in the last 7 months.
:jstutte, could you have a look please?
For more information, please visit auto_nag documentation.

Assignee: gkrizsanits → nobody
Flags: needinfo?(jstutte)

Should we re-triage this? I assume we are in a quite different situation here today?

Flags: needinfo?(jstutte) → needinfo?(bugs)

I hope we don't need anything like this anymore.

Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(bugs)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.