-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TSAN failures in system layer #7803
Comments
@mrjerryjohns FYI |
I'd think the right fix in the short-term is to fix This likely isn't a problem on Darwin. |
The headline issue (for timers) no longer exists after changes in #8800. Arguably that code is locking too much in light of issue #5556, but the cost is isolated. It's required (as in the headline case) due to the SDK-internal threading in
Other current TSAN failures on Linux are:
|
Filed #14890 for the Closing this issue since there are no known failures remaining in system layer. |
Currently chip::System::Object results in multiple TSAN failures but as it is built using the legacy (non-memory-model-aware) gcc __sync builtins it's possible these errors are false positives.
Changing to an implementation built with C++11 primitives will fix this issue, allow enabling TSAN on the unit test suite.
e.g.
./gn_build.sh is_tsan=true is_clang=true
The text was updated successfully, but these errors were encountered: