Closed Bug 1600312 Opened 3 years ago Closed 3 years ago

ThreadSanitizer: data race [@ free] vs. [@ __tsan_atomic64_fetch_sub] involving pointer race [@ mozilla::gfx::SourceSurfaceCapture::~SourceSurfaceCapture]


(Core :: MFBT, defect)

Not set



Tracking Status
firefox72 --- wontfix
firefox73 --- fixed


(Reporter: decoder, Assigned: decoder)


(Blocks 1 open bug)


(Keywords: testcase)

Crash Data


(2 files)

The attached crash information was detected while running CI tests with ThreadSanitizer on mozilla-central revision 66531295716a.

This looks bad because we seem to be racing on a RefPtr. I grepped the test logs and the first test I found that triggered this seemed to be editor/libeditor/tests/test_bug1574596.html.

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.

After seeing a similar pattern in other race reports, I realized that this might be a false positive:

Our thread-safe refcounting uses std::atomic_thread_fence and fences are not supported by TSan currently. I will try to confirm with the developers that this is still the case.

Maybe we can also annotate this somehow.

Component: Graphics → MFBT
Assignee: nobody → choller
Pushed by
Use atomic load instead of fence for RefCounted with TSan. r=froydnj
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla73

I assume this can ride the trains.

You need to log in before you can comment on or make changes to this bug.