Open
Bug 746830
Opened 12 years ago
Updated 2 years ago
nsDirectoryService is not threadsafe even though it uses threadsafe AddRef/Release
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
NEW
People
(Reporter: bent.mozilla, Unassigned)
Details
nsDirectoryService is not threadsafe even though it uses threadsafe AddRef/Release. It accesses a hash table and JS components from whatever thread it is called on, and none of that is safe.
It probably had threadsafe AddRef/Release for use with XPCOM proxies. We should kill that.
|
||
Comment 2•12 years ago
|
||
Yeah, we should refuse to make directory service *usable* on other threads with assertions. I'm not sure I care as much about the refcounting if there's code actually using some kind of hand-rolled proxy, although that really shouldn't be necessary.
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•