<html>
    <head>
      <base href="http://llvm.org/bugs/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - -fsanitize-address enables the leak checker by default"
   href="http://llvm.org/bugs/show_bug.cgi?id=22551">22551</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>-fsanitize-address enables the leak checker by default
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>clang
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>3.5
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>PC
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>Frontend
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>unassignedclangbugs@nondot.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>sstewartgallus00@mylangara.bc.ca
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>llvmbugs@cs.uiuc.edu
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Sometime lately, the leak checker was enabled by default with the address
checker. This is wrong because it breaks otherwise working multiprocess
applications. Often times, a memory leak is of no consequence if it does not
grow over time and is freed when the application exits. However, when the leak
checker is enabled such an application exits with a nonzero exit status even if
it would have exited normally otherwise. In such a case, many monitoring
systems restart the process that exited with a nonzero exit status.

There are two reasonable workarounds I can think of.

Don't enable the leak checker by default with the address sanitizer.

Don't override the application's exit code in the leak checker.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </body>
</html>