Closed Bug 1166207 Opened 5 years ago Closed 4 years ago
Redo preload in the Nuwa process
We need to find an alternative to bug 970307 that is less intrusive and fragile.
Offline discussion with Cervantes indicated that this bug will not be fixed on 2.2. m1, can we pull this off the metabug?
Removing dependency on CAF 2.2, per agreement with partner.
feature-b2g: --- → 2.5+
Whiteboard: [caf priority: p2][CR 840327] → [caf priority: p2][CR 840327][perf-want]
(In reply to Cervantes Yu [:cyu] [:cervantes] from comment #8) > https://treeherder.mozilla.org/#/jobs?repo=try&revision=f51a8759ddf6 Tests with BrowserElement APIs finally passed. Continue with other failures on desktop.
We split preload.js into 2 parts: * The "safe part" that doesn't send out IPC messages to the chrome process. This part is loaded in the Nuwa process. * The "unsafe part" that sends out IPC messages to the chrome process. This part is loaded right after we fork. Detection measures in the IPC channel and nsThread are added to debug and test-enabled builds for breakage from future changes.
Attachment #8646272 - Flags: review?(khuey)
Attachment #8646272 - Flags: review?(khuey) → review+
url: https://hg.mozilla.org/integration/b2g-inbound/rev/dab5325490951ce5a71b99c366bb902f633893cf changeset: dab5325490951ce5a71b99c366bb902f633893cf user: Cervantes Yu <email@example.com> date: Fri Aug 28 17:57:44 2015 +0800 description: Bug 1166207 - Load preload.js in the Nuwa process. r=khuey
Reopen bug per regression found in bug 1200504. Cervantes, please help to review solution again. Many thanks.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
The fix is being reviewed. Clear the ni flag.
Verified in bug 1200504.
Status: REOPENED → RESOLVED
Closed: 5 years ago → 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.