BrowserElementChild.js startup taking ~60 samples (~120ms) on critical startup path

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
6 years ago
6 years ago

People

(Reporter: cjones, Assigned: vingtetun)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

For example, this profile of Template app startup

http://people.mozilla.com/~bgirard/cleopatra/#report=2d71953e8c89fa872949df729c730fe0429b789d

The majority of that time is going to BrowserElementChild._init().  A nontrivial amount of time is also going to cp_init(), which is surprising.
Can we .jsm'ize some of this code for win?
I believe we established some months ago that most of this time in _init went into the first call which touched docShell.  I don't know if preloading about:blank changes this equation.
That doesn't appear to the case in the profile in comment 0, but I admit it's very hard to tell.  (The profile was made with the about:blank preload patch applied.)

Updated

6 years ago
Component: DOM: Apps → DOM: Mozilla Extensions
I think Vivien is working on this incidentally in bug 835809.

Vivien, cp_init() in BrowserElementChild.js is taking a surprising number of samples, ~15 (== ~30ms).  Do you have wins for that?
Assignee: nobody → 21
I may also have improved that in bug 835548, moving from registering N message listeners to a single one.
Not specific enough to be useful anymore.  We've squeezed wins out of this code.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
Component: DOM: Mozilla Extensions → DOM
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.