> Sanitizers ... do not bring the safety to production, since you probably do not want to use sanitizers in production or release

My team runs ASAN in production. We run lots of servers, and we have load balancing that keeps CPU utilization equal across servers. ASAN binaries are slower (maybe 1/2 throughput / 2X "local" cpu-bound latency?) but not so much slower that running it on a small fraction of our servers means we can't meet our SLO. And it's been a huge help to us. Once in a while, we have some segfault that's pretty mysterious otherwise, as the stack trace where memory corruption is discovered can be totally unrelated to the stack trace where the problem was caused. If it happens on the ASAN servers, the root cause is instantly obvious.

TSAN is more problematic to run in production; it's a _lot_ slower.