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? :-)
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.
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
Making pdt+ bugs P1
Priority: P3 → P1
Putting on PDT- radar for beta1. This is not a huge perf hit. Other areas more critical. Would not hold beta for this.
pdt-, pushing to M15
Target Milestone: M14 → M15
Priority: P1 → P3
Target Milestone: M15 → M30
Taking advantage of new "Future" target milestone.
Target Milestone: M30 → Future
dp is no longer @netscape.com. reassigning qa contact to default for this component
QA Contact: dp → rayw
Maybe next time
Keywords: nsbeta1 → nsbeta1-
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".
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 → --
Target Milestone: Future → ---
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.