If that's the case, it's not clear to me that it shouldn't crash the app (versus the alternative of likely corrupting data) in release builds. I guess this is similar to the "assertions should/should not be turned on in release builds" debate, which IMO has good points on both sides.
But maybe there's an extra complicating factor of TSan causing significant performance penalties making it impractical for it to be on in release builds?
But maybe there's an extra complicating factor of TSan causing significant performance penalties making it impractical for it to be on in release builds?