Preload ExtensionContent.jsm

RESOLVED FIXED in Firefox 44

Status

Firefox OS
Runtime
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: ting, Unassigned)

Tracking

(Blocks: 1 bug, {perf})

unspecified
FxOS-S9 (16Oct)
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(firefox44 fixed)

Details

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
In the profile at bug 1210860 comment 9, before loading app content it spends ~120ms on Flame to load frame script extensions.js, most of time spend on importing ExtensionContent.jsm. Preload it to get some improvements.

Note ExtensionContent.init() sends async message through PBrowser to chrome process.
(Reporter)

Comment 1

2 years ago
Created attachment 8672998 [details] [diff] [review]
patch v1
(Reporter)

Comment 2

2 years ago
Comment on attachment 8672998 [details] [diff] [review]
patch v1

With this patch, it now takes ~10ms on Flame for RecvLoadRemoteScript() to run extensions.js.

Since PBrowserChild hasn't been constructed when preload, leave ExtensionContent.init() in the frame script (extensions.js), otherwise sending async message will cause abort.
Attachment #8672998 - Flags: review?(fabrice)
Attachment #8672998 - Flags: review?(fabrice) → review+
https://hg.mozilla.org/mozilla-central/rev/9b32f246edaf
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox44: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → FxOS-S9 (16Oct)

Updated

2 years ago
Keywords: perf
You need to log in before you can comment on or make changes to this bug.