Closed Bug 1682932 Opened 2 years ago Closed 2 years ago

ThreadSanitizer: data race [@ CacheObserver::MemoryCacheCapacity]


(Core :: Networking: Cache, defect, P2)




86 Branch
Tracking Status
firefox86 --- fixed


(Reporter: Gankra, Assigned: Gankra)


(Blocks 1 open bug)


(Whiteboard: [necko-triaged])


(2 files)

Found while bringing up wpt under tsan.

It looks like sAutoMemoryCacheCapacity is an "Initialize Once" static, but doesn't use the adequate machinery for multiple threads racing to run the initializer. Just needs to be wrapped up in one of our Once abstractions. (PR_CallOnce?)

Probably benign since there aren't side-effects and every thread should agree on what value to compute.

Permalink to problematic lines.

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.

Assignee: nobody → a.beingessner
Severity: -- → S2
Priority: -- → P2
Whiteboard: [necko-triaged]

Opted to use this new pattern because PR_CallOnce has issues with tsan.

Pushed by
ensure sAutoMemoryCacheCapacity is properly synchronized. r=valentin,necko-reviewers
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 86 Branch
You need to log in before you can comment on or make changes to this bug.