MTuner是一个免费的多平台内存分析、泄漏检测和分析工具，支持MSVC、GCC和Clang编译器。功能包括:

基于时间轴的内存使用历史和活动内存块 强大的内存操作过滤基于堆，内存标签，时间范围等。 SDK手动仪表与完整的源代码 通过命令行使用支持持续集成 调用堆栈树和树映射导航 更多。

用户可以通过GCC或Clang cross配置任何软件定位平台 编译器。MTuner内置对Windows、PlayStation 4和PlayStation 3平台的支持。

Search your code for occurrences of new, and make sure that they all occur within a constructor with a matching delete in a destructor. Make sure that this is the only possibly throwing operation in that constructor. A simple way to do this is to wrap all pointers in std::auto_ptr, or boost::scoped_ptr (depending on whether or not you need move semantics). For all future code just ensure that every resource is owned by an object that cleans up the resource in its destructor. If you need move semantics then you can upgrade to a compiler that supports r-value references (VS2010 does I believe) and create move constructors. If you don't want to do that then you can use a variety of tricky techniques involving conscientious usage of swap, or try the Boost.Move library.

回答你问题的第二部分，

是否有任何标准或程序可以确保程序中没有内存泄漏。

是的，有。这是C和c++的主要区别之一。

在c++中，永远不要在用户代码中调用new或delete。RAII是一种非常常用的技术，它在很大程度上解决了资源管理问题。程序中的每一个资源(资源是任何需要获取，然后释放的东西:文件句柄，网络套接字，数据库连接，但也包括普通内存分配，在某些情况下，对API调用(BeginX()/EndX()， LockY()， UnlockY()))都应该包装在一个类中，其中:

构造函数获取资源(如果资源是内存分配，则调用new) 析构函数释放资源， 复制和赋值要么被阻止(通过将复制构造函数和赋值操作符设置为私有)，要么被实现为正确工作(例如通过克隆底层资源)

然后，该类在本地、堆栈上或作为类成员实例化，而不是通过调用new和存储指针来实例化。

You often don't need to define these classes yourself. The standard library containers behave in this way as well, so that any object stored into a std::vector gets freed when the vector is destroyed. So again, don't store a pointer into the container (which would require you to call new and delete), but rather the object itself (which gives you memory management for free). Likewise, smart pointer classes can be used to easily wrap objects that just have to be allocated with new, and control their lifetimes.

这意味着当对象超出作用域时，它将被自动销毁，并释放和清理它的资源。

如果在整个代码中始终这样做，就不会有任何内存泄漏。所有可能泄露的内容都绑定到析构函数，该析构函数保证在控件离开声明对象的作用域时被调用。

运行“Valgrind”可以:

1)帮助识别内存泄漏-显示您有多少内存泄漏，并指出代码中泄漏内存分配的行。

2)指出错误的释放内存的尝试(例如不正确的delete调用)

“Valgrind”使用说明

1)在这里获得valgrind。

2)使用-g标志编译代码

3)在shell中运行:

valgrind --leak-check=yes myprog arg1 arg2

其中"myprog"是你编译的程序，arg1, arg2是你程序的参数。

4)结果是一个调用malloc/new的列表，没有后续调用free delete。

例如:

==4230==    at 0x1B977DD0: malloc (vg_replace_malloc.c:136)

==4230==    by 0x804990F: main (example.c:6)

告诉您在哪一行(未释放的)调用了malloc。

正如其他人指出的那样，确保对于每个新的/malloc调用，都有一个后续的delete/free调用。

Valgrind http://valgrind.org/

and

广东发展银行 http://www.gnu.org/software/gdb/

有一些著名的编程技术可以帮助您将内存泄漏的风险降至最低:

if you have to do your own dynamic memory allocation, write new and delete always pairwise, and make sure the allocation/deallocation code is called pairwise avoid dynamic memory allocation if you can. For example, use vector<T> t whereever possible instead of T* t = new T[size] use "smart pointers" like boost smart pointers (http://www.boost.org/doc/libs/1_46_1/libs/smart_ptr/smart_ptr.htm) my personal favorite: make sure you have understood the concept of ownership of a pointer, and make sure that everywhere where you use pointers, you know which code entity is the owner learn which constructors / assignment operators are automatically created by the C++ compiler, and what that means if you have class that owns a pointer (or what that means if you have a class that contains a pointer to an object it does not own).