[Boost-bugs] [ boost-Bugs-1520617 ] Memoryleak when using boost::thread and boost::test together
Bugs item #1520617, was opened at 2006-07-11 19:34 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1520617&group_id=7586 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: threads Group: None Status: Open Resolution: None Priority: 5 Submitted By: SergeiPanov (sergeipanov) Assigned to: Mike Glassford (glassfordm) Summary: Memoryleak when using boost::thread and boost::test together Initial Comment: When I tried to use boost::thread with boost::test (Unit Test Framework) I've always got the followed message: Detected memory leaks! Dumping objects -> {227} normal block at 0x00364698, 24 bytes long. Data: <PS > 50 53 14 00 FF FF FF FF 00 00 00 00 00 00 00 00 {226} normal block at 0x00364428, 8 bytes long. Data: < F6 > 98 46 36 00 01 CD CD CD Object dump complete. It does not matter from Boost version (I tried the latest one as well). The error is reproduced with simple examples from boost::thread docs. Platform: Win32 Compiler: Microsoft Visual C++ version 7.1 STL : Dinkumware standard library version 313 Boost : 1.33.1 Could you help me? Thanks in advance! Sergei Panov ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1520617&group_id=7586 ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Boost-bugs mailing list Boost-bugs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs
----- Original Message ----- From: "SourceForge.net" <noreply@sourceforge.net> Newsgroups: gmane.comp.lib.boost.devel Sent: Tuesday, July 11, 2006 11:34 AM Subject: [Boost-bugs] [ boost-Bugs-1520617 ] Memoryleak whenusing boost::thread and boost::test together
Initial Comment: When I tried to use boost::thread with boost::test (Unit Test Framework) I've always got the followed message: Detected memory leaks! Dumping objects -> {227} normal block at 0x00364698, 24 bytes long. Data: <PS > 50 53 14 00 FF FF FF FF 00 00 00 00 00 00 00 00 {226} normal block at 0x00364428, 8 bytes long. Data: < F6 > 98 46 36 00 01 CD CD CD Object dump complete.
It does not matter from Boost version (I tried the latest one as well). The error is reproduced with simple examples from boost::thread docs.
Platform: Win32 Compiler: Microsoft Visual C++ version 7.1 STL : Dinkumware standard library version 313 Boost : 1.33.1
Could you help me?
These are actually false memory leaks. The memory blocks allocated by boost::thread_specific_ptr will be released after the "memory leak" report. On the other hand, boost::test might want to change the default to not report the memory leaks. Sean
"Sean Huang" <huangsean@hotmail.com> wrote in message news:BAY102-DAV42B46F66FCF9B453BD5E3A3680@phx.gbl...
These are actually false memory leaks. The memory blocks allocated by boost::thread_specific_ptr will be released after the "memory leak" report. On the other hand, boost::test might want to change the default to not report the memory leaks.
It make sense to report memory leaks by default. In case if used prefer the opposite, one could use either CLA or environment variable to configure this behavior. Gennadiy
----- Original Message ----- From: "Gennadiy Rozental" <gennadiy.rozental@thomson.com> Newsgroups: gmane.comp.lib.boost.devel Sent: Wednesday, July 12, 2006 12:12 PM Subject: Re: [Boost-bugs] [ boost-Bugs-1520617 ]Memoryleakwhenusing boost::thread and boost::test together
It make sense to report memory leaks by default. In case if used prefer the opposite, one could use either CLA or environment variable to configure this behavior.
At least it should be documented (or print out a warning message) that memory leak detection on Windows reports false leaks sometimes (anytime boost::thread and boost::thread_specific_ptr are used). These kinds issues are very difficult and time consuming to track down and are very surprising to new users and that's why I suggested changing the default. Advanced users that want to use leak detectors should know about the limitations. Sean
participants (3)
-
Gennadiy Rozental -
Sean Huang -
SourceForge.net