Closed
Bug 59434
Opened 24 years ago
Closed 8 years ago
nsHTTPHandler is not thread safe
Categories
(Core :: Networking: HTTP, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Future
People
(Reporter: darin.moz, Unassigned)
References
Details
(Keywords: perf)
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22 i686; en-US; m18) Gecko/20001107 Netscape6/6.0 BuildID: 2000110709 nsHTTPHandler is not thread safe. This could potentially cause all sorts of havoc b/c calls to nsHTTPChannel::OpenInputStream can spawn a new thread for the HTTP transaction, which in turn makes calls to the nsHTTPHandler. For that matter, even nsIOService appears not to be thread safe! This is a serious problem which needs to be resolved. Reproducible: Always Steps to Reproduce: 1.<n/a> Actual Results: major parts of necko are not thread safe Expected Results: we expect that it should be since it is possible to open new threads from within necko.
Reporter | ||
Updated•24 years ago
|
Component: Networking → Networking: HTTP
Reporter | ||
Updated•24 years ago
|
Target Milestone: --- → Future
Reporter | ||
Updated•18 years ago
|
Assignee: darin → nobody
QA Contact: tever → networking.http
Comment 1•17 years ago
|
||
http://mxr.mozilla.org/seamonkey/source/netwerk/protocol/http/src/nsHttpHandler.cpp#1386 It appears to be threadsafe, and like that since revision 1.2 of the file. Is this FIXED then?
Comment 2•17 years ago
|
||
that doesn't mean that the class is threadsafe, only that its addref and release functions are.
Comment 3•8 years ago
|
||
1240568 and 1240569 should address this
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•