Re: [boost] Are memory leaks reported by Boost.Test Microsoft Memory Leak Detection Enabling spurious or real?
Regarding this problem, I've found more details about it on the Visual Studio Connect website: http://connect.microsoft.com/VisualStudio/feedback/details/106937/memory-lea... typeinfo is used by the unit test framework if you use BOOST_AUTO_TEST_CASE_TEMPLATE. Few fixes that seem reasonable: All use the following tools: _CrtMemCheckpoint [1] and _CrtMemDumpAllObjectsSince [2] available since VS2003 to report objects in specific regions Few reasonable cases: * For the entire test path, if dumping enabled, checkpoint before all tests start, dump after all tests complete * For each test suite, checkpoint before suite starts, dump after suite ends (complicated by nested suites...) * For each test case, checkpoint before test starts, dump after test ends 1: http://msdn.microsoft.com/en-us/library/h3z85t43(v=vs.90).aspx 2: http://msdn.microsoft.com/en-us/library/hhy09244(v=vs.90).aspx -- Thomas Harning Jr.
[Thomas Harning Jr.]
This has been fixed in VC11, but unfortunately you'll need to deal with it in VC10 and earlier. Stephan T. Lavavej Visual C++ Libraries Developer
Stephan T. Lavavej-2 wrote:
Stephan, (I'm sorry of this is off-topic, but I think it's related) By the way, I must say since I started using the Microsoft Connect I've been struggling to understand the bug reports management happening over there. This one is a good example of the issues I'm referring to. You confirmed the bug has been fixed in V11, but the ticket is marked as "Closed as Won't Fix". It is confusing and misinforming. I've been using bug reporting systems of dozens projects and in all cases the "wontfix" flag means what it says - no action has been taken and none is planned to be taken. Best regards, Mateusz ----- -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org -- View this message in context: http://boost.2283326.n4.nabble.com/Re-Are-memory-leaks-reported-by-Boost-Tes... Sent from the Boost - Dev mailing list archive at Nabble.com.
[Thomas Harning Jr.]
http://connect.microsoft.com/VisualStudio/feedback/details/106937/memory-lea...
[STL]
This has been fixed in VC11, but unfortunately you'll need to deal with it in VC10 and earlier.
[mloskot]
Look at the history - it was resolved as Won't Fix on 5/19/2006, half a year before I joined the VC team. I had to find the bug in our old, old, old bug database (we've had separate databases for VC8, VC9, VC10, and VC11), using an old program (our internal Product Studio; now we use Team Foundation Server), just to reply to the bug, as a courtesy to anyone stumbling upon it. I didn't know if I could mess with the resolution state (yes, it should be marked as Fixed), so I left it as is. I can't fix the past. I can fix only the future. STL
On 05/01/11 18:25, Stephan T. Lavavej wrote:
I see.
Understood. Thanks for the explanation. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org
Is anyone going to document this somewhere? (where? Boost/Test docs?) I'm sure many people will be worried (as I was) about these spurious leaks. Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow@hetp.u-net.com
participants (5)
-
Mateusz Loskot -
mloskot
-
Paul A. Bristow -
Stephan T. Lavavej -
Thomas Harning Jr.