<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/59112>59112</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            leak sanitizer reports are painfully slow under docker in some circumstances
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            new issue
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          avikivity
      </td>
    </tr>
</table>

<pre>
    Under docker, the process can sometimes start with elevated RLIMIT_NOFILE (ulimit -n). Then, if a leak is detected (even if suppressed) this loop will spend minutes of CPU time closing billions of files:

https://github.com/llvm/llvm-project/blob/2e999b7dd1934a44d38c3a753460f1e5a217e9a5/compiler-rt/lib/sanitizer_common/sanitizer_posix_libcdep.cpp#L465

Much better to use close_range() if available.


Semi-related: https://github.com/llvm/llvm-project/issues/48067

</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJydUk1v2zAM_TX2hYhhS3YSHXzY2hUIkG7D1p4DWaJjrbJkSHK67tePdrqtO26AoC-Sj4-P7Lx-aR-dxgDaqycMGbuBNCBMwSuMEZR0EP2IyYwYISYZEjybNABavMiEGr4cD_eHh9PHT3eH4wfI2H62ZjQJNi5jooCHAd0CanqQYFE-gYmgMaFagskdL-gWa5ynKVBK1BRHHMjNej9RNmshTug0jMbNiWj4Hm4-P8LCCZT10bgzdORmvFuNvbEYM_4uK2-z8nUfUprWP3ZH60wlzF2h_EgPay-_jg3V_Y2o0bOzvqODoRCi22ldCV7LutZ8r7jcNbzeln2FjWTVDoVsyJXQJsocNmGJt2YJj9KZZH5gOJF19O6vr4mofz-Ro9I4FWqaMsaP9bZ5y_t-VgN0mBK1KHmY47VkPAXpzkj6LWot4l6ksbKzWLyNvu5fcTSbgHbpF0kA_6yFiXEmRdldvS-3uytojm213Yqybkohct1yLbiQeTLJYrs2-nehEHDyIUWQgSZLGtfP1r5AtP4Z5jfDB-Y6bKBMUPNI0-ZoCPM52Pb_KTeiqlg-tELVvS513YladVuu9F5IZF3FqL-cY5WTemhjmzXvM8YcPsMKQfesuc1Ny0rGCKmqGr6vRFHWPaGUXAjsu74qs7rEkVpQLDwKH855aFdK3XyOZLQmpvjHKGM0Z4e4piN8OafBh1ZezJO5mPSSr8nblfxPX7MxjA">