Closed Bug 1599481 Opened 5 years ago Closed 5 years ago

Implement async process launching

Categories

(Core :: DOM: Navigation, enhancement, P3)

Product:
Core
Component:
DOM: Navigation
Type:
enhancement

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1602712
Project Flags:
Fission Milestone M6

People

(Reporter: neha, Assigned: Yoric)

References

Details

(Whiteboard: [fxperf:p2])

We want to implement this in order to not block the main thread in the parent to do a process launch. This will implement the idea here: https://searchfox.org/mozilla-central/rev/8b7aa8af652f87d39349067a5bc9c0256bf6dedc/docshell/base/CanonicalBrowsingContext.cpp#238-250 .

Blocks: 1490803
Fission Milestone: --- → M6
Priority: -- → P3
Whiteboard: [fxperf]

The plan we came up with a while ago in the IPC meeting was to refactor ContentParent::GetNewOrUsedBrowserProcess so that the “or used” part would be its own function (returning null or Nothing in the case where there isn't already a process), leaving a relatively small part to be made async (using ContentParent::LaunchProcessAsync).

Whiteboard: [fxperf] → [fxperf:p2]
Assignee: nobody → dteller

Ah, typo-ed my patches to the other bug. Reversing the DUP.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.