Boost C++ Libraries: Ticket #737: Memory leaks in adjacency_list? https://svn.boost.org/trac10/ticket/737 <pre class="wiki">Hello, I've been in fight with memory leaks in my application for some days. And now I found that most memory is losing while using adjacency_list&lt;&gt; (boost 1.33.1 + VC++6.0). Basically we've lost about 100Kb after each graph life cycle (created - changed - removing). Moreover, I guess, I found the similar problem on the very simple test: #include "..\boost_1_33_1\boost\graph\adjacency_list.hpp" using namespace boost; typedef adjacency_list&lt;&gt; Graph; void main() { int num_vertex = 10000; Graph* graph = new Graph(); for(int j=0; j&lt;num_vertex; ++j) { add_vertex(graph); } delete graph; } Here I've lost some memory too (about 20 Kb). Maybe I'm doing something wrong? Thanks _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users </pre> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/737 Trac 1.4.3 Douglas Gregor Thu, 22 Mar 2007 18:39:27 GMT status changed https://svn.boost.org/trac10/ticket/737#comment:1 https://svn.boost.org/trac10/ticket/737#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">assigned</span> → <span class="trac-field-new">closed</span> </li> </ul> <pre class="wiki">Logged In: YES user_id=249098 Originator: YES I've been doing a bunch of testing with this code and a variety of adjacency_list instances, using manual object tracking and valgrind to look for leaks, but as far as I can tell none of the configurations of adjacency_list are leaking any memory. I don't know if this is a system-dependent problem or a false alarm (memory pooling can sometimes trick leak detectors into seeing leaks that aren't there), but I'm closing this bug unless we get further information that there is, in fact, a leak. </pre> Ticket