Closed
Bug 512588
Opened 15 years ago
Closed 8 years ago
create fastload, compreg, etc. files as part of standard profile install
Categories
(Core Graveyard :: Profile: BackEnd, defect, P3)
Core Graveyard
Profile: BackEnd
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: vlad, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [ts])
With a new profile, we currently go through the fastload, compreg, etc. steps each time; this leads to a really bad first-run experience for new Firefox users, because that process is extremely slow. Instead, given that we know exactly what should be in these, we should use the PGO run (or on platforms were we don't do PGO a single startup, or on cross-compile platforms ~~magic~~) to create the faststart, compreg, etc. files so that we can just copy these into place when we set up the first profile and use it directly, without requiring registration and restart.
Reporter | ||
Updated•15 years ago
|
Whiteboard: [ts]
Comment 1•15 years ago
|
||
Alternatively we should do the -silent thing at the end of our installers like the good old days. I reimplemented this for mobile in bug 469076. I think the proper way to fix is to redesign our *fastload* and ship our js modules/components as precompiled binaries.
Updated•15 years ago
|
Priority: -- → P3
Blocks: 1243899
Comment 3•8 years ago
|
||
This bug is filed in a bugzilla component related to pre-Firefox code which no longer exists. I believe it is no longer relevant and I am therefore closing it INCOMPLETE. If you believe that this bug is still valid and needs to be fixed, please reopen it and move it to the Toolkit:Startup and Profile System product/component.
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•