Closed
Bug 846576
Opened 11 years ago
Closed 3 years ago
TSan: Thread data race nsHttpChannel vs. nsHttpConnectionMgr (in nsCString::SetCharAt vs. nsCharTraits<char>::compare)
Categories
(Core :: Networking: HTTP, defect, P3)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: decoder, Unassigned)
Details
(Keywords: sec-want, Whiteboard: [tsan][tsan-test-blocker][necko-backlog][qa-not-actionable])
Attachments
(1 file)
|
15.65 KB,
text/plain
|
Details |
During Firefox start-up with ThreadSanitizer (LLVM version r176045), we get a data race reported as described in the attached log. Trace was created on mozilla-central with changeset 885cde564ff3. According to the TSan devs, most of the reported traces should be real data races, even though they can be "benign". We need to determine if the race can/should be fixed, or put on the ignore list. Even for benign races, TSan devs suggest to fix them (second priority), as they can also cause problems [1]. [1] http://software.intel.com/en-us/blogs/2013/01/06/benign-data-races-what-could-possibly-go-wrong
|
Reporter | |
Updated•11 years ago
|
Component: XPCOM → Networking: HTTP
|
||
Updated•8 years ago
|
Whiteboard: [tsan][tsan-test-blocker] → [tsan][tsan-test-blocker][necko-backlog]
|
||
Comment 1•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
|
|
||
Comment 2•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
|
||
Updated•3 years ago
|
Whiteboard: [tsan][tsan-test-blocker][necko-backlog] → [tsan][tsan-test-blocker][necko-backlog][qa-not-actionable]
|
|
Reporter | |
Comment 3•3 years ago
|
||
Unlikely to be still an issue after this time and with this amount of CI we have on TSan by now.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•