MSan can easily produce logs that are so large that we cannot even download them, which makes them useless!
Most of such logs look like this:
[2026/03/26 12:26:27.262] ==179902==__tls_get_addr: DTLS_Find 0x7f060c2666e0 2 [2026/03/26 12:26:27.262] ==179902==__tls_get_addr: DTLS_Find 0x7f060b7616e0 2 [2026/03/26 12:26:27.262] ==179902==__tls_get_addr: DTLS_Find 0x7f060b7616e0 2 [2026/03/26 12:26:27.262] ==179902==__tls_get_addr: DTLS_Find 0x7f060b7616e0 2 [2026/03/26 12:26:27.262] ==179902==__tls_get_addr: DTLS_Find 0x7f060b7616e0 2 [2026/03/26 12:26:27.262] ==179902==__tls_get_addr: DTLS_Find 0x7f060b7616e0 2 [2026/03/26 12:26:27.262] ==179902==__tls_get_addr: DTLS_Find 0x7f060b7616e0 2 [2026/03/26 12:26:27.262] ==179902==__tls_get_addr: DTLS_Find 0x7f060b7616e0 2 [2026/03/26 12:26:27.262] ==179902==__tls_get_addr: DTLS_Find 0x7f060b7616e0 2
To avoid this, it seems that we may need to decrease the verbosity level all the way to verbosity=1.