Closed
Bug 46358
Opened 25 years ago
Closed 16 years ago
nsSupportsWeakReference::GetWeakReference() isn't thread safe
Categories
(Core :: XPCOM, defect, P3)
Core
XPCOM
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: beard, Unassigned)
References
()
Details
See the blame URL above, on line 75 of nsWeakReference.cpp, there's a test to see
if mProxy is NULL, and if it is a new nsWeakReference is created and assigned to
mProxy. This isn't thread-safe and could cause leaks of weak references. Do we
ever use weak references across multiple threads?
|
||
Updated•25 years ago
|
Status: NEW → ASSIGNED
|
|
||
Updated•25 years ago
|
QA Contact: leger → kandrot
|
||
Comment 1•23 years ago
|
||
taking some of the bugs that I have been working on from scc.
Assignee: scc → dougt
Status: ASSIGNED → NEW
|
|
||
Updated•23 years ago
|
Target Milestone: --- → mozilla1.1
|
|
||
Updated•23 years ago
|
Target Milestone: mozilla1.1alpha → Future
|
|
||
Updated•19 years ago
|
QA Contact: kandrot → nobody
|
||
Updated•19 years ago
|
Assignee: dougt → nobody
QA Contact: nobody → xpcom
|
||
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•