Click here to Skip to main content
15,867,453 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Old times I've used the BoundsChecker for C++ memory leaks detection. It was very good for 32 bit but never worked 100% under 64 bit, no newer API's support, so we dropped this tool.
- Just wonder how nowdays the C++ developers cope with the memory leaks?
Now I'm working with Visual Studio 2015. Any new tools/techniques to fight the memory leaks?

Thanks.

What I have tried:

nothing yet ......................
Posted
Updated 30-Jan-20 5:05am

VS dumps all unreleased memory blocks in the output window upon normally ending a program in debug mode.

Other than that, the only suggestion I can make is using smart pointers in your code, rather than raw pointers.
 
Share this answer
 
Comments
oleg63 30-Jan-20 11:31am    
Thanks, but it's not the ultimate solution to problems with the large mixed languages code base.

Waiting for the Address Sanitizer to be able work on 64-bit.
Stefan_Lang 31-Jan-20 3:18am    
Ok, if you have such a large code base:

We've used Clang Power Tools, but memory leaks are not exactly it's strength. Might still be worth a look. I've found that after running code through clang-tidy and format, errors that are still in your code become much more obvious
Using Visual Studio 2015, you have built-in profiler. There may be others but this one works pretty well.

Check Here!.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900