Closed Bug 1133053 Opened 9 years ago Closed 3 years ago

TSan: multiple data races connected to media/webrtc/signaling/src/media-conduit/RunningStat.h

Categories

(Core :: WebRTC: Signaling, defect, P5)

x86_64
Linux
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: froydnj, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [tsan])

Attachments

(1 file)

Attached file webrtc-stat-races.txt
[cribbing from decoder's script, hopefully he won't mind]

The attached logfile shows a thread/data race detected by TSan (ThreadSanitizer).

Typically, races reported by TSan are not false positives, but it is possible that the race is benign. Even in this case though, we should try to come up with a fix unless this would cause unacceptable performance issues. Also note that seemingly benign races can possibly be harmful (also depending on the compiler and the architecture) [1].

If the bug cannot be fixed, then this bug should be used to either make a compile-time annotation for blacklisting or add an entry to the runtime blacklist.

There are multiple races in the attached file; examples could be multiplied.  I don't think these races are necessary harmful, as they appear to be gathering statistics for telemetry, but it'd be good if we could add appropriate atomic annotations or *something* for them so that TSan can understand what's going on.

[1] http://software.intel.com/en-us/blogs/2013/01/06/benign-data-races-what-could-possibly-go-wrong
backlog: --- → webRTC+
Rank: 45
Priority: -- → P4
Mass change P4->P5 to align with new Mozilla triage process.
Priority: P4 → P5

Webrtc signaling was moved in bug 1664900. In the new files, I can't seem to find an equivalent to these stack traces and they don't match any of our existing webrtc suppressions.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: