Understanding memory leak output

[raul_figous]

Hi Guys,

Iam back again. This time with a different issue. I want to understand the information on memory leaks provided in the output window. Like for instance,


//////////////////////////////////////////////////////////////////
Detected memory leaks!
Dumping objects ->
{75001} normal block at 0x0291A438, 1020 bytes long.
Data: <è µ > E8 02 B5 00 00 00 00 00 00 00 00 00 00 00 00 00
strcore.cpp(118) : {74998} normal block at 0x028EEA70, 24 bytes long.
Data: < L I > 01 00 00 00 05 00 00 00 05 00 00 00 4C 00 49 00
strcore.cpp(118) : {74973} normal block at 0x01D95AA0, 44 bytes long.
Data: < 0 0 > 01 00 00 00 0F 00 00 00 0F 00 00 00 30 00 30 00
strcore.cpp(118) : {74970} normal block at 0x01D95938, 44 bytes long.
Data: < C C > 01 00 00 00 0F 00 00 00 0F 00 00 00 43 00 43 00
{74969} client block at 0x01D958D0, subtype 0, 36 bytes long.
a CObject object at $01D958D0, 36 bytes long
{74955} normal block at 0x01E16B00, 6 bytes long.
Data: < > 01 00 00 00 00 00
{74954} normal block at 0x01E210E8, 6 bytes long.
Data: < > 01 00 00 00 00 00
{74953} normal block at 0x02919DF8, 826 bytes long.
Data: < %ë! %ë! > 01 00 00 00 00 00 00 00 25 EB 21 01 25 EB 21 01
{74952} normal block at 0x01E0E7E8, 12 bytes long.
Data: < Ž¦1 Ž¦1 > 01 00 00 00 8E A6 31 01 8E A6 31 01
{74951} normal block at 0x02919D90, 30 bytes long.
Data: < Ž¦1 Ž¦1 > 01 00 00 00 8E A6 31 01 8E A6 31 01 04 00 00 00
{74950} normal block at 0x02919A18, 826 bytes long.
Data: < > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
plex.cpp(31) : {74949} normal block at 0x02919960, 124 bytes long.
Data: < x�‘ > 00 00 00 00 00 00 00 00 00 00 00 00 78 94 91 02
{74948} normal block at 0x02919478, 1188 bytes long.
Data: <| > 7C 19 1E 02 01 00 00 00 00 00 00 00 00 00 00 00
{74947} normal block at 0x02919020, 1044 bytes long.
Data: <|¿ > 7C BF 10 10 01 00 00 00 00 00 00 00 00 00 00 00
{74946} normal block at 0x01E16550, 12 bytes long.
Data: < > 01 00 00 00 00 00 00 00 00 00 00 00
{74945} normal block at 0x02925F70, 20 bytes long.
Data: < ˆÃ*Ñ > 01 00 00 00 08 00 00 00 00 00 00 00 88 ED D1 01
{74944} normal block at 0x02918F70, 20 bytes long.
Data: < ÿÿÿÿÿÿÿÿdÃ*Ñ > 00 00 00 00 FF FF FF FF FF FF FF FF 64 ED D1 01
{74943} normal block at 0x01E26788, 8 bytes long.
Data: <p ‘ p_’ > 70 8F 91 02 70 5F 92 02
{74942} normal block at 0x02925E68, 192 bytes long.

//////////////////////////////////////////////////////////////////////////////


Where will i go into the source and find out which part of the code is giving me this leak?
I have no clue on this. Guys who have the knowledge of finding out and understand the above given code immediately after seeing this can also give me some suggestion on how they do that. I know mfc provides CMemoryState class with many functions in it. But how to use them efficiently to handle the situation?

raul
(spain)

[wneat]

Why not using bouncechecker? A powerful tool on memory leak checking.

[raul_figous]

Using third party tools does not give u proper understanding of things happening inside. Ok thats one solution what u have mentioned. But i want to know the meaning of the code listed and where should i start from.

raul

[vicodin451]

Originally posted by Andreas Masur in many, many threads

• Detecting Memory Leaks
• Detecting Memory Leaks in MFC

[raul_figous]

thank you mate.

raul

[kandukondein]

Apart from the links provided by Vicodin do use Call Stack with warmest regards as it helps in getting memory leaks in other third party dlls that u might use in ur application.

Regards
Kandukondein