[feature] performance on first launch reqs. xpcom/test/regFactory hook up in installer

VERIFIED FIXED in M11

Status

SeaMonkey
Installer
P2
critical
VERIFIED FIXED
19 years ago
13 years ago

People

(Reporter: leger, Assigned: Suresh Duddi (gone))

Tracking

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [Perf])

(Reporter)

Description

19 years ago
TO DO for Performance Improvement:
We are loading every dll in the components directory and instructing
it to auto-register.  Could we have a utility that does this similar
to regsvr32.  This also takes a lot of time when first initializing
AppRunner.  For some reason the initialization code seems to load the
components even after they are auto-registered.
(Reporter)

Updated

19 years ago
Whiteboard: [Perf]
(Reporter)

Updated

19 years ago
Target Milestone: M7

Updated

19 years ago
Assignee: cyeh → dp
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
Priority: P3 → P2
Target Milestone: M7 → M8
(Assignee)

Comment 1

19 years ago
We need this and have to turn off autoregister. But before that we need to work
out the registry problems and decide where it is going to be. The registry stuff
will work out in M7. Moving this to M8.

Updated

19 years ago
Blocks: 7251

Updated

19 years ago
Blocks: 9164
(Assignee)

Updated

19 years ago
Assignee: dp → chofmann
Status: ASSIGNED → NEW
Target Milestone: M8 → M9
(Assignee)

Comment 2

19 years ago
We have this utility. xpcom/test/regFactory

Once the installer is ready, we will need to use this in the installer.

M9 and moving it to installer group.

Updated

19 years ago
Assignee: chofmann → cathleen
Summary: Need a utility similar to regsvr32 → [feature] performance on first launchy reqs. xpcom/test/regFactory hook up in installer

Comment 3

19 years ago
changing the summary and moving over the cathleen to set target milestone
and get this baby hooked up.

Updated

19 years ago
Blocks: 11020

Updated

19 years ago
Summary: [feature] performance on first launchy reqs. xpcom/test/regFactory hook up in installer → [feature] performance on first launch reqs. xpcom/test/regFactory hook up in installer

Updated

19 years ago
Assignee: cathleen → ssu
Component: Build Config → Install Wizard
OS: Windows 95 → All
Hardware: PC → All
Target Milestone: M9 → M10

Comment 4

19 years ago
change component to Install Wizard.
setting target milestone to M10.
reassign to Sean (for win), ccing Samir (for mac), Dan, Cathleen & DP.

DP, I assume this utility exists on Mac too, correct?
(Reporter)

Updated

19 years ago
QA Contact: cyeh → gbush
(Reporter)

Comment 5

19 years ago
Setting QA Contact to gbush to keep her in the loop.

Updated

19 years ago
Status: NEW → ASSIGNED

Comment 6

19 years ago
The wizard now launches apprunner with a -installer parameter at the end of the
install.  If autoregistering is suppose to be happening only with the -installer
flag now, then this bug is fixed for Windows.

If the -installer is not the fix for this bug, someone please provide more
information.  I'm leaving this bug open because the Mac is probably not done
yet.
(Assignee)

Updated

19 years ago
Assignee: ssu → dp
Status: ASSIGNED → NEW
(Assignee)

Comment 7

19 years ago
I will take this bug. I need to make:
- -installer do autoreg instead of always
- use buildID and run autoreg only if the buildID changed for release builds
only
- Land relative pathnames in registry
- Ship component registry along with the release

Updated

19 years ago
Blocks: 12806

Comment 8

19 years ago
Dp, do you think using a different flag (other than -installer) to run the
autoreg might be useful?  I'm thinking of the situation when the user simply
wants to autoreg, not also go through the entire profile migration.

This way the profile migration and the autoreg can be run either independent of
each other or together at the same time (like apprunner.exe -installer -autoreg)

Just a thought.
xpinstall will be able to run autoreg apart from the -installer flag, and
power users will be able to manually call RegFactory.exe (which I'd rename to
regcomp or compreg).

Would blowing away the component registry trigger an AutoReg?
(Assignee)

Comment 10

19 years ago
Yeah there are ton of ways to get to autoreg. So I dont think another flag would
be more useful.
(Assignee)

Updated

19 years ago
Target Milestone: M10 → M11
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 11

19 years ago
We are in home stretch. component.reg can be shipped.

regfactory has been updated to do autoreg if run with no arguments. But release
cant run it because it is a test/ and they dont compile tests. Need to move
regFactory to something like xpcom/registry
(Assignee)

Updated

18 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
(Reporter)

Comment 12

18 years ago
Is there any more clean up work to do here?  OR is this totally Resolved/Fixed
now?  Wanted to check before marking Verified.  Thanks!
(Reporter)

Updated

18 years ago
Status: RESOLVED → VERIFIED
(Reporter)

Comment 13

18 years ago
Checked with dp..cool to mark Verified.
(Reporter)

Comment 14

18 years ago
Updating component from Install Wizard to Installer.

Updated

17 years ago
No longer blocks: 7251
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.