Registry file opening should use nsIFile

RESOLVED WONTFIX

Status

()

RESOLVED WONTFIX
19 years ago
10 years ago

People

(Reporter: sfraser_bugs, Unassigned)

Tracking

({helpwanted, perf})

Trunk
helpwanted, perf
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
For performance reasons, we should use an nsFileSpec when opening the components
registry file (and other registry files) if at all possible. On Mac, the
nsFileSpec to full path conversion takes around 14ms on a fast machine,
which accounts for 6% of the time spent in NS_InitXPCOM. There will be another
slowdown in the standard library when the full path is converted back to an
FSSpec to open the file.
Could this wait until after beta? We'll want to make some speed improvements
then, too, right? :-)
(Reporter)

Comment 2

19 years ago
I fear that items that get pushed to 'after beta' will be dropped because of
schedule pressure. This isn't a huge performance hit, so it could wait. But if
you are doing any other related registry work, you might consider this too.

Updated

19 years ago
Target Milestone: M15

Updated

19 years ago
Keywords: perf
Summary: [Perf] Registry file opening should use nsFileSpec → Registry file opening should use nsFileSpec
Needs to be Beta
Target Milestone: M15 → M14
Need to convert the registry over to the new nsIFile.
Summary: Registry file opening should use nsFileSpec → Registry file opening should use nsIFile

Updated

19 years ago
Blocks: 16464

Updated

19 years ago
Keywords: beta1
Making pdt+ bugs P1
Priority: P3 → P1

Comment 6

19 years ago
Putting on PDT- radar for beta1.  This is not a huge perf hit.  Other areas more 
critical.  Would not hold beta for this.
Whiteboard: [PDT-]
pdt-, pushing to M15
Target Milestone: M14 → M15
Keywords: helpwanted
Priority: P1 → P3
Target Milestone: M15 → M30
Taking advantage of new "Future" target milestone.
Target Milestone: M30 → Future

Comment 9

18 years ago
dp is no longer @netscape.com. reassigning qa contact to default for this component
QA Contact: dp → rayw
Maybe next time
Keywords: nsbeta1 → nsbeta1-

Updated

18 years ago
Blocks: 58668

Comment 11

17 years ago
Hasn't this been bug fixed by dougt lately??

--pete
This bug is targeted at a Mac classic platform/OS, which is no longer supported
by mozilla.org. Please re-target it to another platform/OS if this bug applies
there as well or resolve this bug.

I will resolve this bug as WONTFIX in four weeks if no action has been taken.
To filter this and similar messages out, please filter for "mac_cla_reorg".
(Reporter)

Updated

15 years ago
OS: Mac System 8.5 → All
Hardware: Macintosh → All

Updated

10 years ago
Component: XPCOM Registry → XPCOM
QA Contact: rayw → xpcom
This bug hasen't been touched for years and is clearly unowned. Moving back to default assignee/QA so that people, who are watching those can accurately triage this bug.

Also resetting Priority, Target Milestone, Status Whiteboard and Status.
Assignee: dveditz → nobody
Status: ASSIGNED → NEW
Priority: P3 → --
Whiteboard: [PDT-]
Target Milestone: Future → ---

Updated

10 years ago
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.