On Thursday, July 7, 2016 at 8:42:42 PM UTC-4, Gavin Lambert wrote: > > On Thursday, June 30, 2016 at 11:58:38 AM UTC+12, Jeffrey Walton wrote: >> >> >> Still an issue in Windows, as far as I know: >> http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=106937 >> > > Connect issues seem to be private now, so I can't actually view that. I'm > happy to treat it as a false positive though, as I said before. > > What about the issue with Gunzip and SignatureVerificationFilter though? >
If the library that tracks and reports leaks is unloaded before the memory is freed, then it will report the leak. The best I can tell, the references to misc.h and integer.cpp are static objects. They apparently outlive the DLL reporting them as leaks. If interested, you might try to force the load order of libraries. In this case, your leak checking DLL should be loaded before the Crypto++ library. You can usually control library load order by using `#pragma comment(lib, "xxx")`. You may have to build from the command line if the pragma does not work. Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
