3

当我运行以下代码时：

#include "gmock/gmock.h"
#include "gtest/gtest.h"

#define _CRTDBG_MAP_ALLOC
#include <crtdbg.h>

int main(int argc, char **argv) 
{
    ::testing::InitGoogleTest(&argc, argv);
    _CrtDumpMemoryLeaks();
    return 0;
}

我得到以下输出：

Detected memory leaks!
Dumping objects ->
{652} normal block at 0x00074CE0, 4 bytes long.
 Data: < L  > 98 4C 07 00 
{651} normal block at 0x00074C98, 12 bytes long.
 Data: <,           > 2C 03 1B 01 00 00 00 00 00 00 00 00 
{650} normal block at 0x00074C50, 8 bytes long.
 Data: <hI      > 68 49 07 00 00 00 00 00 
{649} normal block at 0x00074C10, 4 bytes long.
 Data: <t   > 74 03 1B 01 
{648} normal block at 0x00074BC8, 8 bytes long.
 Data: <xK      > 78 4B 07 00 00 00 00 00 
{647} normal block at 0x00074B70, 28 bytes long.
 Data: <         K   L  > BC 01 1B 01 01 CD CD CD C8 4B 07 00 E0 4C 07 00 
{646} normal block at 0x00074B28, 8 bytes long.
 Data: < I      > 18 49 07 00 00 00 00 00 
{645} normal block at 0x00074AE0, 8 bytes long.
 Data: < I      > 04 49 07 00 00 00 00 00 
{644} normal block at 0x00074A98, 8 bytes long.
 Data: < H      > DC 48 07 00 00 00 00 00 
{643} normal block at 0x00074A50, 8 bytes long.
 Data: < H      > C8 48 07 00 00 00 00 00 
{642} normal block at 0x00074A08, 8 bytes long.
 Data: < H      > B4 48 07 00 00 00 00 00 
{641} normal block at 0x000749C0, 8 bytes long.
 Data: < H      > A0 48 07 00 00 00 00 00 
{640} normal block at 0x00074E90, 1 bytes long.
 Data: < > 00 
{639} normal block at 0x00074870, 272 bytes long.
 Data: <        t    N  > 20 03 1B 01 CD CD CD CD 74 FA 1B 01 90 4E 07 00 
{638} normal block at 0x00074F68, 72 bytes long.
 Data: <C:\Users\Baz> 43 3A 5C 55 73 65 72 73 5C 45 42 41 52 47 52 49 
{637} normal block at 0x00074E48, 8 bytes long.
 Data: <hO  G   > 68 4F 07 00 47 00 00 00 
{616} normal block at 0x00074EE0, 72 bytes long.
 Data: <C:\Users\Baz> 43 3A 5C 55 73 65 72 73 5C 45 42 41 52 47 52 49 
{595} normal block at 0x00074828, 8 bytes long.
 Data: <        > F0 F9 1B 01 00 00 00 00 
{594} normal block at 0x000747E8, 1 bytes long.
 Data: < > 00 
{561} normal block at 0x000747A0, 5 bytes long.
 Data: <fast > 66 61 73 74 00 
{496} normal block at 0x00074760, 1 bytes long.
 Data: < > 00 
{311} normal block at 0x00074720, 1 bytes long.
 Data: < > 00 
{282} normal block at 0x000746E0, 2 bytes long.
 Data: <* > 2A 00 
{253} normal block at 0x00074698, 5 bytes long.
 Data: <auto > 61 75 74 6F 00 
Object dump complete.

我究竟做错了什么？

4

2 回答 2

5

除了接受的答案之外，谷歌文档还指出：

由于静态初始化的 Google Test 单例需要在堆上分配，Visual C++ 内存泄漏检测器将在程序运行结束时报告内存泄漏。避免这种情况的最简单方法是使用 _CrtMemCheckpoint 和 _CrtMemDumpAllObjectsSince 调用来不报告任何静态初始化的堆对象。有关更多详细信息和其他堆检查/调试例程，请参阅 MSDN。

这涉及在_CrtMemCheckPoint之后::testing::InitGoogleTest调用，然后在_CrtMemDumpAllObjectsSince之后调用RUN_ALL_TESTS()。主函数看起来有点像这样：

::testing::InitGoogleTest(&argc, &argv);
// Get a checkpoint of the memory after Google Test has been initialized.
_CrtMemState memoryState = {0};
_CrtMemCheckpoint( &memoryState );
int retval = RUN_ALL_TESTS();

// Check for leaks after tests have run
_CrtMemDumpAllObjectsSince( &memoryState );
return retval;

不幸的是，如果测试失败，Google 测试会导致内存泄漏，这意味着这不是一个完美的解决方案。

于 2013-10-17T15:16:31.897 回答
3

你没有做错什么。“内存泄漏”来自静态初始化的谷歌测试单例类的堆分配。

这是来自谷歌测试常见问题的答案：如何抑制 Windows 上的内存泄漏消息？

于 2012-10-03T09:48:18.010 回答