Closed
Bug 845504
Opened 13 years ago
Closed 5 years ago
TSan: Thread data race in makewt_32(void) vs. cftmdl_128_SSE2(float *a)
Categories
(Core :: WebRTC, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox22 | --- | affected |
backlog | webrtc/webaudio+ |
People
(Reporter: posidron, Assigned: jesup)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [tsan][tsan-test-blocker])
Attachments
(1 file)
16.36 KB,
text/plain
|
Details |
During initial tests with ThreadSanitizer (LLVM version), we get a data race reported as described in the attached log. Trace was created on mozilla-central with changeset 122820:c233837cce08.
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
Assignee | ||
Comment 1•13 years ago
|
||
Race on access to cftmdl_wk1r - in this case, something is reading it in AEC processing before it gets inited in WebRtcAec_InitAec(). Upstream issue 1503
https://code.google.com/p/webrtc/issues/detail?id=1503
Not sure if FF21 is affected.
Impact would likely be temporary AEC mis-training/worked at start, if this were to actually occue.
status-firefox22:
--- → affected
Assignee | ||
Comment 2•13 years ago
|
||
Not sure about blocking yet
Assignee: nobody → rjesup
Priority: -- → P2
Whiteboard: [tsan][tsan-test-blocker] → [tsan][tsan-test-blocker][webrtc][webrtc-blocking?]
Updated•13 years ago
|
Whiteboard: [tsan][tsan-test-blocker][webrtc][webrtc-blocking?] → [tsan][tsan-test-blocker][webrtc][blocking-webrtc?]
Assignee | ||
Comment 3•13 years ago
|
||
Blocking- since I think the worst case here (which is unlikely in practice) would be a mis-initialization or failure of the AEC
Whiteboard: [tsan][tsan-test-blocker][webrtc][blocking-webrtc?] → [tsan][tsan-test-blocker][webrtc][blocking-webrtc-]
Assignee | ||
Comment 4•12 years ago
|
||
this appears to be audio sample insertion racing against enabling of the AEC. It shouldn't be a suppressed TSAN hit, it should avoid trying to run the AEC before init is finished.
Updated•10 years ago
|
backlog: --- → webRTC+
Rank: 22
Whiteboard: [tsan][tsan-test-blocker][webrtc][blocking-webrtc-] → [tsan][tsan-test-blocker]
Comment 5•8 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Comment 6•6 years ago
|
||
Clearing sec-want based on C3
Comment 7•5 years ago
|
||
This was fixed upstream 8 years ago, and it appears we have since uplifted the fixes (or otherwise made this irrelevant).
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•