{"id":237,"date":"2017-05-11T03:21:52","date_gmt":"2017-05-11T03:21:52","guid":{"rendered":"http:\/\/imalogic.com\/blog\/?p=237"},"modified":"2020-09-28T10:04:50","modified_gmt":"2020-09-28T10:04:50","slug":"how-to-hunt-memory-leaks-using-visual-studio","status":"publish","type":"post","link":"https:\/\/imalogic.com\/blog\/2017\/05\/11\/how-to-hunt-memory-leaks-using-visual-studio\/","title":{"rendered":"How to hunt memory leaks using Visual Studio"},"content":{"rendered":"

Make sure you compile debug version of your project.<\/p>\n

\n

Press F5 (Start Debugging)<\/p>\n

Do whatever you suspect to leak memory, and close program.<\/p>\n

In output window you should see:<\/p>\n

Detected memory leaks!
\nDumping objects ->
\n{8677} normal block at 0x01AA4E08, 68 bytes long.
\nData: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD
\nObject dump complete.<\/code><\/p>\n

Add:

\n#ifdef _DEBUG
\n#define _CRTDBG_MAP_ALLOC
\n#define _INC_MALLOC
\n#endif
<\/code><\/p>\n

in your stdafx.h file, and recompile whole solution.<\/p>\n

Now it should be something like:<\/p>\n

Detected memory leaks!
\nDumping objects ->
\nC:\\Program Files\\Microsoft Visual Studio 8\\VC\\include\\crtdbg.h(1147) : {8677} normal block at 0x01AA4E08, 68 bytes long.
\nData: < > CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD
\nObject dump complete.<\/code><\/p>\n

The problem is it shows allocator code, not your allocation itself. Still not very usefull. Now tricky part. Double click<\/p>\n

C:\\Program Files\\Microsoft Visual Studio 8\\VC\\include\\crtdbg.h\u00a0<\/em>line.<\/p>\n

Set a trap (F9\/Debug->Toggle Breakpoint) right click on the red dot and select condition and type _Size==<your leak size in this case 68><\/em>. Next time you will debug, program will stop if there will be 68 bytes allocated, then you can select Debug->Windows->Call Stack<\/em> and if you are lucky you will see your memory leak.<\/p>\n<\/div>\n

Hunt memory leaks using Visual Studio & Deleaker<\/h1>\n

Another way to hunt memory leaks is using a useful tools called Deleaker.<\/strong><\/a><\/p>\n

Deleaker is a plugin for Visual Studio, when you enable it, you have access to the deleaker windows.<\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

When you perform a execution of your program in debug, deleaker start to analyse your code and provide you all information about memory leaks.<\/p>\n

I have made a basic test with a array of object without deleting all created object. Deleaker have detected all unreleased objects ( 10 Hits ).<\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n\n\n

The screenshot above show when i release correctly all objects. Deleaker do the job \ud83d\ude42<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

Above, the deleaker configuration options\u2026<\/p>\n\n\n\n

<\/p>\n<\/body>","protected":false},"excerpt":{"rendered":"

Make sure you compile debug version of your project. Press F5 (Start Debugging) Do whatever you suspect to leak memory,<\/p>\n","protected":false},"author":1,"featured_media":304,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[7,66,2,1],"tags":[24,35,32,34,33],"class_list":["post-237","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-coding","category-computer-graphics","category-demo","category-uncategorized","tag-c","tag-debug","tag-memory-leaks","tag-microsoft","tag-visual-studio"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/imalogic.com\/blog\/wp-content\/uploads\/2017\/05\/memoty_leak_android.jpg?fit=690%2C335&ssl=1","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8J21V-3P","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/imalogic.com\/blog\/wp-json\/wp\/v2\/posts\/237","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/imalogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/imalogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/imalogic.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/imalogic.com\/blog\/wp-json\/wp\/v2\/comments?post=237"}],"version-history":[{"count":2,"href":"https:\/\/imalogic.com\/blog\/wp-json\/wp\/v2\/posts\/237\/revisions"}],"predecessor-version":[{"id":867,"href":"https:\/\/imalogic.com\/blog\/wp-json\/wp\/v2\/posts\/237\/revisions\/867"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/imalogic.com\/blog\/wp-json\/wp\/v2\/media\/304"}],"wp:attachment":[{"href":"https:\/\/imalogic.com\/blog\/wp-json\/wp\/v2\/media?parent=237"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/imalogic.com\/blog\/wp-json\/wp\/v2\/categories?post=237"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/imalogic.com\/blog\/wp-json\/wp\/v2\/tags?post=237"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}