Hey Antonio, 2010/12/1 Antonio Mancina <[email protected]>: > 8 bytes in 1 blocks are still reachable in loss record 1 of 4 > at 0x4C275D8: malloc (vg_replace_malloc.c:236) > by 0x625713C: boost::detail::get_once_per_thread_epoch() (in > /usr/lib/libboost_thread.so.1.40.0) > by 0x625160F: ??? (in /usr/lib/libboost_thread.so.1.40.0) > by 0x6251718: boost::detail::get_current_thread_data() (in > /usr/lib/libboost_thread.so.1.40.0) > by 0x6251738: boost::detail::find_tss_data(void const*) (in > /usr/lib/libboost_thread.so.1.40.0) > by 0x6251788: boost::detail::get_tss_data(void const*) (in > /usr/lib/libboost_thread.so.1.40.0) > by 0x51AB7B3: > Wt::WebSession::Handler::attachThreadToHandler(Wt::WebSession::Handler*) > (tss.hpp:82)
These are thread-specific data that we set, using functions from the boost thread library. Apparently, there is a memory leak with respect to this thread specific data. This memory leak does however not grow with the number of threads or the number of manipulations of thread specific data, so is in its own quite innocent. But perhaps we need to report this with the boost authors. Regards, koen ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
