Hacker ApprovedDepartments

ThreadSanitizer

Shares rank 5 of 6 sanitizers by recommenders

Developers recommend it as a free tool for finding threading bugs during testing, run alongside other sanitizers.

Developers recommend it as a free tool for finding threading bugs during testing, run alongside other sanitizers.

6 people gave an opinion

recommend it
5
criticize it
1
approval share
83%
Each figure is one person. RecommendsCriticizes

Recommended in 3 of 13 months

  1. November 2025: not recommended
  2. December 2025: not recommended
  3. January 2026: recommended
  4. February 2026: recommended
  5. March 2026: not recommended
  6. April 2026: not recommended
  7. May 2026: not recommended
  8. June 2026: not recommended
  9. July 2026: not recommended
  10. August 2026: not recommended
  11. September 2026: not recommended
  12. October 2026: recommended
  13. November 2026: not recommended (month in progress)

Why it doesn’t carry the badge

  • 5 people recommend itNeeds 10 or more, not met.
  • 5 recommenders for every criticNeeds 2 to 1 or better, met.
  • Recommended in 3 of 13 monthsNeeds 4 or more, not met.

The same three rules apply to every product, and the badge can’t be bought. How the badge works

What people say about it

The reasons people give, with the number of comments that give each one. Open a reason to read what they said.

Why people recommend it

Each mark is one comment

  • Recommended alongside other sanitizers

    “Ultimately TSAN and KTSAN exist for a reason, and rust devs should learn how to use them effectively.”

    Comment from 13 Oct 2026 in “11 year old unsoundness bugs found in Rust borrow checker”

    “build and test with sanitizers (ASAN, UBSAN, TSAN) when not measuring performance”

    Comment from 10 Oct 2026 in “C for Rust programmers”

    “clang-tidy, ASAN, UBSAN, LSAN, MSAN, and TSAN are AMAZING”

    Comment from 13 Jan 2026 in “LLVM: The Bad Parts”
  • Used in routine testing

    “build and test with sanitizers (ASAN, UBSAN, TSAN) when not measuring performance”

    Comment from 10 Oct 2026 in “C for Rust programmers”

    “test with ASAN, UBSAN and TSAN”

    Comment from 14 Oct 2026 in “Arena Allocators in C”

Other sanitizers people recommend

The four most recommended other sanitizers, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.

ThreadSanitizer compared with 4 alternatives
ProductRecommendCriticizeApprovalMonthsOwnedBadge
Valgrind29878%13—Approved
Miri26390%12—Approved
AddressSanitizer21484%7—Approved
UndefinedBehaviorSanitizer120100%5—Approved
ThreadSanitizerThis page5183%3——
See all 6 sanitizers, ranked

What people said

All 6 comments that mention it, newest first. Each links to the original comment.

“test with ASAN, UBSAN and TSAN”

RecommendsComment from 14 Oct 2026 in “Arena Allocators in C”

“Ultimately TSAN and KTSAN exist for a reason, and rust devs should learn how to use them effectively.”

RecommendsComment from 13 Oct 2026 in “11 year old unsoundness bugs found in Rust borrow checker”

“build and test with sanitizers (ASAN, UBSAN, TSAN) when not measuring performance”

RecommendsComment from 10 Oct 2026 in “C for Rust programmers”

“they only guarantee much less than a better language does”

CriticizesComment from 9 Oct 2026 in “Reducing undefined behavior in the C language”

“already have several years of production experience, in a mature ecosystem”

RecommendsComment from 16 Feb 2026 in “Zig – io_uring and Grand Central Dispatch std.Io implementations landed”

“clang-tidy, ASAN, UBSAN, LSAN, MSAN, and TSAN are AMAZING”

RecommendsComment from 13 Jan 2026 in “LLVM: The Bad Parts”

Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.