On Wed, 3 Feb 2010, Derek Gaston wrote: > So... I'm trying to turn off reference counting with > --disable-reference-counting... but I'm still getting "Memory Leak > Detected!" errors at the end of my run. > > Besides the obvious "Fix the memory leak!"... is there something > else I need to do to make this message go away? I really don't > understand how it can be getting to this point if I've disabled > reference counting.
Disabling reference counting is a little misleading - the ReferenceCountedObjects increment a static threadsafe int in each constructor and decrement it in each destructor regardless of configure settings. What --enable-reference-counting turns on (with NDEBUG off) is just the per-class map that breaks down the results into counts on each object type. Surprised me too, actually. I think it would be better to turn off counting entirely when asked via configure (especially since it requires an atomic unsigned int when threading is on), do the "one total count" stuff in opt mode with counting on, then do the detailed stuff in dbg/devel mode with counting on. --- Roy ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
