Open Bug 781622 Opened 13 years ago Updated 3 years ago

Profile XPCOM initialization in content process

Categories

(Core :: XPCOM, defect)

Product:
Core
Component:
XPCOM
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

()

People

(Reporter: cjones, Unassigned)

References

Details

Initial measurements (on Nexus S) show it taking ~400-450 ms. This appears to be the single biggest chunk of startup overhead currently (after a pending fix). We should profile startup to see where the time is going. bsmedberg suggests there may be some IO wins. A pre-forked "template process" wouldn't ameliorate this problem, without significant reworking of XPCOM init.
khuey, is your xpt-in-C stuff applicable here?
Maybe. Depends on what we're spending time on.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.