Open
Bug 487181
Opened 15 years ago
Updated 2 years ago
DownloadScanner shouldn't be on the critical path in DownloadManager's getService
Categories
(Toolkit :: Downloads API, enhancement)
Tracking
()
NEW
People
(Reporter: timeless, Unassigned)
Details
Attachments
(1 file)
4.93 KB,
text/plain
|
Details |
If at all possible, DownloadScanner should not be initialized from the main thread. I know you have this wonderful comment talking about threadsafety, and i know that i'm working on improving the threadsafety story, but your code scared me because my browser got stuck in nsDownloadScanner::EnumerateOAVProviders for a while. fwiw, I have Symantec Client Security, and this is an Opt build of my own (w/ a bunch of patches, but none to download manager....)
Comment 1•15 years ago
|
||
You are running XP w/o SP2 I take it? Otherwise we would be using IAE. I am very surprised that enumeration is taking so long because AFAIK, it is just enumerating through a particular key in the registry. Can you tell me exactly what function inside EnumerateOAVProviders is taking a while?
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•