<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 7/30/2018 7:18 AM, Michael Wojcik
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:MWHPR18MB1037715B5E921780A2C546D4F92F0@MWHPR18MB1037.namprd18.prod.outlook.com">I
don't know why people worry about singleton memory "leaks". If the
leak isn't growing over the lifetime of the process, it's not
causing any trouble. I've seen some teams obsessing about getting
clean reports from dynamic-analysis tools like Valgrind. In most
environments that's pointless "optimization" and a waste of
development resources.</blockquote>
<br>
Because a zero-leaks policy is a lot easier to manage than having to
make a judgement call on each leak whether or not it's important,
and having to filter out "unimportant" leaks when you're trying to
find out whether you've introduced any "important" leaks.<br>
<br>
Maybe the test suite only caused the program to leak one buffer, but
that doesn't tell you whether a real workload (or a malicious
workload) will leak gigabytes.<br>
<pre class="moz-signature" cols="72">--
Jordan Brown, Oracle Solaris</pre>
</body>
</html>