WinDbug 发现程序内存溢出的地方

在使用com的过程中,发现无论是vs2005还是boundscheck都找不到内存泄露,但是程序一跑起来, 很快就上几十M的内存泄露. 找啊找啊找, 找了半天, 还是没发现. 求助同事, 他采用了windbg, 不过好像也不是那么简单, 很多时候甚至于需要一个函数一个函数通过console方式来进行测试.

 

总结一下, 在使用com编程的时候需要注意的地方:

1，确保CoInitialize() 与 UncoInitalize() 的配对使用， 由于com是需要在线程内初始化的，因此每个线程都需要进行初始化和关闭。对于自由线程，可以通过CoInitalizeEx()来初始化，在其他所有线程内都可以调用此线程产生的组件。当然最后还是需要通过UncoInitialize()来释放。

2，确保所有对象/组件在使用前与使用后的reference是相同的，也就是说每次引用与解引用必须成对出现，可以通过检查对象/组件的reference来确认。

3，确保所有create出来的零时组件/对象都已经销毁，很多时候创建出来的零时组件/对象没有用到，但是忘记了手动删除，也是会出现内存泄露的

4，确保new出来的组件/对象/数组等，通过正确的方式进行释放，譬如new出来的数组，必须通过 delete[] 来进行释放。

 

以上是一些体会，因为很难用工具有效的定位内存泄露区域，所有一定要在编写代码是注意以上几点。

 

这里转一篇基于windbg查找内存泄露的文章：

 zz: http://www.codeproject.com/KB/cpp/MemoryLeak.aspx

 

Introduction

Memory leak is a time consuming bug often created by C++ developers. Detection of memory leaks is often tedious. Things get worst if the code is not written by you, or if the code base is quite huge.

Though there are tools available in the market that will help you in memory leak detection, most of these tools are not free. I found Windbg as a freeware powerful tool to solve memory leak bugs. At least, we get an idea about the code location which might be suspected to cause memory leaks. COM Interface leaks are out of the scope of this article.

Windbg is a powerful user/kernel space debugger from Microsoft, which can be downloaded and installed from here.

Using Windbg

To start working with Windbg:

1. Configure the symbol file path to the Microsoft symbol server “SRV*d:/symbols*http://msdl.microsoft.com/download/symbols”.
2. Add your program EXE/DLL PDB (program database) path to the symbol file path.
3. You also need to to configure the Operating System's flag to enable user stack trace for the process which has memory leaks. This is simple, and can be done with gflags.exe. Gflags.exe is installed during Windbg's installation. This can also be done through command line, using the command “gflags.exe /i MemoryLeak.exe +ust”. My program name is Test2.exe; hence, for the demo, I will be using Test2.exe rather than MemoryLeak.exe. The snapshot below shows the setting of OS flags for the application Test2.exe.

 

Once we have configured Windbg for the symbol file path, start the process which is leaking memory, and attach Windbg to it. The Attach option in Windbg is available under the File menu, or can be launched using the F6 shortcut. The snapshot below shows the same:

 

The !heap command of Windbg is used to display heaps. !heap is well documented in the Windbg help.

I have developed a small program which leaks memory, and will demonstrate further using the same.

 Collapse Copy Code

int _tmain(int argc, _TCHAR* argv[]){   while(1)      {         AllocateMemory();      }      return 0; } void AllocateMemory() {      int* a = new int[2000];      ZeroMemory(a, 8000);      Sleep(1); }

The above program leaks an integer array of size 2000*4 bytes.

After attaching Windbg to the process, execute the !heap –s command. -s stands for summary. Below is the output of the !heap -s for the leaking process:

 Collapse Copy Code

0:001> !heap -sNtGlobalFlag enables following debugging aids for new heaps:    validate parameters    stack back traces  Heap     Flags   Reserv  Commit  Virt   Free  List   UCR  Virt  Lock  Fast                     (k)     (k)    (k)     (k) length      blocks cont. heap -----------------------------------------------------------------------------   00150000 58000062    1024     12     12      1     1     1    0      0   L     00250000 58001062      64     24     24     15     1     1    0      0   L     00260000 58008060      64     12     12     10     1     1    0      0         00330000 58001062   64576  47404  47404     13     4     1    0      0  -----------------------------------------------------------------------------

Let the process execute for some time, and then re-break in to the process, and execute !heap -s again. Shown below is the output of the command:

 Collapse Copy Code

0:001> !heap -sNtGlobalFlag enables following debugging aids for new heaps:   validate parameters   stack back traces   Heap     Flags   Reserv  Commit  Virt   Free  List   UCR  Virt  Lock  Fast                      (k)     (k)    (k)     (k) length      blocks cont. heap    -----------------------------------------------------------------------------    00150000 58000062    1024     12     12      1     1     1    0      0   L      00250000 58001062      64     24     24     15     1     1    0      0   L      00260000 58008060      64     12     12     10     1     1    0      0          00330000 58001062  261184 239484 239484     14     4     1    0      0         -----------------------------------------------------------------------------

Lines marked in bold show the growing heap. The above snapshot shows a heap with the handle 00330000 growing.

Execute “!heap -stat –h 00330000” for the growing heap. This command shows the heap statistics for the growing heap. Shown below is the command's output.

 Collapse Copy Code

0:001> !heap -stat -h 00330000heap @ 00330000group-by: TOTSIZE max-display: 20    size     #blocks     total     ( %) (percent of total busy bytes)    1f64 76c6 - e905f58  (99.99)    1800 1 - 1800  (0.00)    824 2 - 1048  (0.00)    238 2 - 470  (0.00)    244 1 - 244  (0.00)    4c 5 - 17c  (0.00)    b0 2 - 160  (0.00)    86 2 - 10c  (0.00)    50 3 - f0  (0.00)    74 2 - e8  (0.00)    38 4 - e0  (0.00)    48 3 - d8  (0.00)    c4 1 - c4  (0.00)    62 2 - c4  (0.00)    be 1 - be  (0.00)    b8 1 - b8  (0.00)    ae 1 - ae  (0.00)    ac 1 - ac  (0.00)    55 2 - aa  (0.00)    a4 1 - a4  (0.00)

The above snapshot shows 0x76c6 blocks of size 1f64 being allocated (marked in bold). Such a huge number of blocks of the same size makes us suspect that these can be leaked blocks. Rest of the block allocations do not have growing block numbers.

The next step is to get the address of these blocks. Use the command !heap -flt s 1f64. This command filters all other blocks of heap and displays the details of blocks having size 1f64.

Shown below is the output for the command:

 Collapse Copy Code

0:001> !heap -flt s 1f64    _HEAP @ 150000    _HEAP @ 250000    _HEAP @ 260000    _HEAP @ 330000      HEAP_ENTRY Size Prev Flags    UserPtr UserSize - state        003360e0 03f0 0000  [07]   003360e8    01f64 - (busy)        00338060 03f0 03f0  [07]   00338068    01f64 - (busy)        00339fe0 03f0 03f0  [07]   00339fe8    01f64 - (busy)        0033bf60 03f0 03f0  [07]   0033bf68    01f64 - (busy)        0033dee0 03f0 03f0  [07]   0033dee8    01f64 - (busy)        01420040 03f0 03f0  [07]   01420048    01f64 - (busy)        01421fc0 03f0 03f0  [07]   01421fc8    01f64 - (busy)        01423f40 03f0 03f0  [07]   01423f48    01f64 - (busy)        01425ec0 03f0 03f0  [07]   01425ec8    01f64 - (busy)        01427e40 03f0 03f0  [07]   01427e48    01f64 - (busy)        01429dc0 03f0 03f0  [07]   01429dc8    01f64 - (busy)        0142bd40 03f0 03f0  [07]   0142bd48    01f64 - (busy)        0142dcc0 03f0 03f0  [07]   0142dcc8    01f64 - (busy)        0142fc40 03f0 03f0  [07]   0142fc48    01f64 - (busy)        01431bc0 03f0 03f0  [07]   01431bc8    01f64 - (busy)        01433b40 03f0 03f0  [07]   01433b48    01f64 - (busy)        01435ac0 03f0 03f0  [07]   01435ac8    01f64 - (busy)        01437a40 03f0 03f0  [07]   01437a48    01f64 - (busy)        014399c0 03f0 03f0  [07]   014399c8    01f64 - (busy)        0143b940 03f0 03f0  [07]   0143b948    01f64 - (busy)        0143d8c0 03f0 03f0  [07]   0143d8c8    01f64 - (busy)        0143f840 03f0 03f0  [07]   0143f848    01f64 - (busy)        014417c0 03f0 03f0  [07]   014417c8    01f64 - (busy)        01443740 03f0 03f0  [07]   01443748    01f64 - (busy)        014456c0 03f0 03f0  [07]   014456c8    01f64 - (busy)        01447640 03f0 03f0  [07]   01447648    01f64 - (busy)        014495c0 03f0 03f0  [07]   014495c8    01f64 - (busy)        0144b540 03f0 03f0  [07]   0144b548    01f64 - (busy)        0144d4c0 03f0 03f0  [07]   0144d4c8    01f64 - (busy)        0144f440 03f0 03f0  [07]   0144f448    01f64 - (busy)        014513c0 03f0 03f0  [07]   014513c8    01f64 - (busy)        01453340 03f0 03f0  [07]   01453348    01f64 - (busy)        014552c0 03f0 03f0  [07]   014552c8    01f64 - (busy)        01457240 03f0 03f0  [07]   01457248    01f64 - (busy)        014591c0 03f0 03f0  [07]   014591c8    01f64 - (busy)        0145b140 03f0 03f0  [07]   0145b148    01f64 - (busy)        0145d0c0 03f0 03f0  [07]   0145d0c8    01f64 - (busy)        0145f040 03f0 03f0  [07]   0145f048    01f64 - (busy)        01460fc0 03f0 03f0  [07]   01460fc8    01f64 - (busy)        01462f40 03f0 03f0  [07]   01462f48    01f64 - (busy)        01464ec0 03f0 03f0  [07]   01464ec8    01f64 - (busy)        01466e40 03f0 03f0  [07]   01466e48    01f64 - (busy)        01468dc0 03f0 03f0  [07]   01468dc8    01f64 - (busy)

Use any UsrPtr column value from the listed output, and then use the the command !heap -p -a UsrPtr to display the call stack for UsrPtr. I have selected 0143d8c8 marked in bold.

Upon execution of !heap -p -a 0143d8c8, we get the call stack shown below:

 Collapse Copy Code

0:001> !heap -p -a 0143d8c8     address 0143d8c8 found in    _HEAP @ 330000      HEAP_ENTRY Size Prev Flags    UserPtr UserSize - state        0143d8c0 03f0 0000  [07]   0143d8c8    01f64 - (busy)        Trace: 0025        7c96d6dc ntdll!RtlDebugAllocateHeap+0x000000e1        7c949d18 ntdll!RtlAllocateHeapSlowly+0x00000044        7c91b298 ntdll!RtlAllocateHeap+0x00000e64        102c103e MSVCR90D!_heap_alloc_base+0x0000005e        102cfd76 MSVCR90D!_heap_alloc_dbg_impl+0x000001f6        102cfb2f MSVCR90D!_nh_malloc_dbg_impl+0x0000001f        102cfadc MSVCR90D!_nh_malloc_dbg+0x0000002c        102db25b MSVCR90D!malloc+0x0000001b        102bd691 MSVCR90D!operator new+0x00000011        102bd71f MSVCR90D!operator new[]+0x0000000f        4113d8 Test2!AllocateMemory+0x00000028        41145c Test2!wmain+0x0000002c        411a08 Test2!__tmainCRTStartup+0x000001a8        41184f Test2!wmainCRTStartup+0x0000000f        7c816fd7 kernel32!BaseProcessStart+0x00000023

The lines marked in bold shows the functions from our code.

Note: Sometimes, it might happen that the “!heap -s” command does not show a growing heap. In that case, use the “!heap -stat -h” command to list all the heaps with their sizes and number of blocks. Spot the growing number of blocks, and then use the “!heap –flt s SIZE” (SIZE = the size of the suspected block) command.