Closed Bug 835001 Opened 12 years ago Closed 12 years ago

Creating and initializing remote app frame consuming 120-140ms on critical startup path

Categories

(Core Graveyard :: DOM: Apps, defect)

Product:
Core Graveyard
Component:
DOM: Apps
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: cjones, Assigned: fabrice)

Details

This time is all spent inside appendFrame() in the gaia window_manager.js. The breakdown is approximately - 70% doing BrowserElementParent init and sundry observer notifications - 10% under gaia's createFrame(), which actually creates the iframe element. This is triggering the 70% work above, obviously. - remaining ~20% in various C++ things related to app init Profile is http://people.mozilla.com/~bgirard/cleopatra/#report=38fcb0169ca5f710c80508b04e5a37dcd4446d2d, but you have to be able to see the right view.
Whiteboard: [FFOS_perf]
Assignee: nobody → fabrice
Chris, is this a dupe of the BEP refactoring?
Whiteboard: [FFOS_perf]
Yeah, this is all covered by more specific items now.
No longer blocks: 834622
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.