https://svn.boost.org/trac10/ticket/2689 <p> It looks like using cache_begin&lt; true &gt; option with unordered containers with link_mode&lt; auto_unlink &gt; can lead to subtle crashes in run time. Supposedly, the problem appears when the leading node of the container (the one that is pointed to by begin()) is deleted without explicitly erasing the element from the container. In that case begin() returns an iterator to a non-existing element. </p> <p> This issue is not highlighted in the docs or checked in the code. It would be great if the container checked this options combination and did not compile in the first place. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/2689 Trac 1.4.3 Ion Gaztañaga Wed, 25 Mar 2009 17:41:39 GMT https://svn.boost.org/trac10/ticket/2689#comment:1 https://svn.boost.org/trac10/ticket/2689#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> <li><strong>milestone</strong> <span class="trac-field-old">Boost 1.38.0</span> → <span class="trac-field-new">Boost 1.39.0</span> </li> </ul> <p> Static assertion added to check it at compile time and also a note in the documentation. Revision 51971 in trunk. </p> Ticket