&gt; I&#x27;m actually not even sure what you mean when you say use after free - I rarely expose a naked pointer, and when I do the lifetime and ownership are pretty obvious.<p>Reference and iterator invalidation, usually.<p>&gt; I think you are misjudging the reality of working in C++11 - memory leaks and use after free don&#x27;t seem to be an issue to me after having done nothing but C++11 for three years.<p>It continues to be an issue for us and every other browser vendor, despite widespread adoption of C++11 throughout the codebase. Large C++ apps that are believed immune to UAF typically just haven&#x27;t been the target of people actively looking for holes.