Closed Bug 1690370 Opened 2 years ago Closed 2 years ago

ThreadSanitizer: data race [@ NullifyConsumeBodyPump] vs. [@ operator]


(Core :: DOM: Workers, defect)

Not set



87 Branch
Tracking Status
firefox87 --- fixed


(Reporter: jkratzer, Assigned: edenchuang)


(Blocks 2 open bugs)



(2 files)

The attached crash information was detected while running CI tests with ThreadSanitizer on mozilla-central revision 20210202-57bcdf857d44.

For detailed crash information, see attachment.
General information about TSan reports
Why fix races?

Data races are undefined behavior and can cause crashes as well as correctness issues. Compiler optimizations can cause racy code to have unpredictable and hard-to-reproduce behavior.

If you think this race can cause crashes or correctness issues, it would be great to rate the bug appropriately as P1/P2 and/or indicating this in the bug. This makes it a lot easier for us to assess the actual impact that these reports make and if they are helpful to you.
False Positives / Benign Races

Typically, races reported by TSan are not false positives [1], but it is possible that the race is benign. Even in this case it would be nice to come up with a fix if it is easily doable and does not regress performance. Every race that we cannot fix will have to remain on the suppression list and slows down the overall TSan performance. Also note that seemingly benign races can possibly be harmful (also depending on the compiler, optimizations and the architecture) [2][3].

[1] One major exception is the involvement of uninstrumented code from third-party libraries.
[3] How to miscompile programs with "benign" data races:
Suppressing unfixable races

If the bug cannot be fixed, then a runtime suppression needs to be added in mozglue/build/TsanOptions.cpp. The suppressions match on the full stack, so it should be picked such that it is unique to this particular race. The bug number of this bug should also be included so we have some documentation on why this suppression was added.

This is racing on the value of mShuttingDown, although weirdly in this case both threads are setting it to true? So pretty benign but potentially an indication that something more scary could be happening.

Naive fix is to just make mShuttingDown atomic.

Permalink to problematic lines:




It seems to me that the callback in BodyConsumer::Create should rather dispatch its action to the worker's owning thread. There are other callbacks that already dispatch to a different thread, such as

Hi Eden, can you take a look here? Thanks!

Flags: needinfo?(echuang)

Oh it occurs to me that Bug 1686156 is probably strongly related to this one.

Assignee: nobody → echuang
Flags: needinfo?(echuang)
Pushed by
Remove race condition on BodyConsumer::mShuttingDown r=dom-worker-reviewers,sg
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 87 Branch
You need to log in before you can comment on or make changes to this bug.