&gt; Search the Chromium and Firefox bug trackers.<p>Hardly standup examples of good C++ code.<p>Take the latest use-after-free in Chrome to date, namely CVE-2015-6765, from the top of[0], The fix for that is was [1], and adds a memory safe standard container (std::set) to keep hold of some objects to change object lifetime. I&#x27;ve looked at it for about 3 minutes and I can tell immediately that the entire implementation of the &quot;appcache update&quot; functionality is a complete hack job. There are variables and calls everywhere keeping track of, and querying, state. There are multiple containers holding objects in different states being manipulated all in the same routine, and this fix adds another. If a &quot;job&quot; can&#x27;t outlive its &quot;fetchers&quot; then why don&#x27;t the fetchers own them?<p>Raw pointers everywhere, this pointers being passed around... &quot;DeleteSoon&quot;... excessive assertions...it&#x27;s amazing at how much ugly, poorly structured, and scary looking code can be packed in to one file.<p>I would argue this is a data point in favour of a correlation between programmer skill and frequency of vulnerabilities. Whoever wrote this clearly knows C++, but they don&#x27;t know how to write good code.<p>[0] <a href="http:&#x2F;&#x2F;www.cvedetails.com&#x2F;vulnerability-list&#x2F;vendor_id-1224&#x2F;product_id-15031&#x2F;opec-1&#x2F;Google-Chrome.html" rel="nofollow">http:&#x2F;&#x2F;www.cvedetails.com&#x2F;vulnerability-list&#x2F;vendor_id-1224&#x2F;...</a><p>[1] <a href="https:&#x2F;&#x2F;codereview.chromium.org&#x2F;1463463003&#x2F;diff&#x2F;20001&#x2F;content&#x2F;browser&#x2F;appcache&#x2F;appcache_update_job.cc" rel="nofollow">https:&#x2F;&#x2F;codereview.chromium.org&#x2F;1463463003&#x2F;diff&#x2F;20001&#x2F;conten...</a>