Closed Bug 394486 Opened 17 years ago Closed 7 years ago

GetShortPathNameW is slow

Categories

(Firefox :: File Handling, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: pavlov, Assigned: bsmedberg)

References

Details

(Keywords: perf)

I've been profiling startup and noticing that we're spending quite a bit of time in GetShortPathNameW().  The main offender is from this stack:

GetShortPathNameW
nsLocalFile.EnsureShortPath
nsLocalFile.Equals
IndexOfDirectoryOfFile
xptiSortFileList
NS_QuickSort
xptiInterfaceInfoManager.BuildOrderedFileArray
xptiInterfaceInfoManager.DoFullValidationMergeFromFileList
xptiInterfaceInfoManager.AutoRegisterInterfaces
xptiInterfaceInfoManager.GetInterfaceInfoManagerNoAddRef
NS_InitXPCOM3_P


Now that we no longer support Win95/98/ME can we get away with either converting short file names to long filenames to avoid conflicts or just doing away with this code entirely?
We cannot do away with the code entirely, but I'm pretty sure we can try normalizing to long paths to see if that's less expensive.
Product: Core → Firefox
Version: Trunk → unspecified
nsLocalFile.Equals still calls EnsureShortPath which calls ::GetShortPathName. But I really doubt we still do any of this during startup (especially now that xpt files are in omni.ja), so I think this is either worksforme or wontfix.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
See Also: → 1863957
You need to log in before you can comment on or make changes to this bug.