Detecting memory leaks windows

Kernel-mode memory leaks usually deplete nonpaged pool, causing the Pool Nonpaged Bytes counter to increase, although pageable memory can be affected as well. Occasionally these counters may show false positives because an application is caching data. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No.

Any additional feedback? Submit and view feedback for This product This page. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. A memory leak occurs when a process allocates memory from the paged or nonpaged pools, but does not free the memory.

As a result, these limited pools of memory are depleted over time, causing Windows to slow down. If memory is completely depleted, failures may result. Determining Whether a Leak Exists describes a technique you can use if you are not sure whether there is a memory leak on your system. Community Bot 1 1 1 silver badge.

I didn't mean that I wanted to detect leaks using these calls, sorry if my statement was unclear. I only meant that I wanted to detect possible leaks of memory that had been allocated using the CoTask calls. My program receives media frames from a network source. These media frames must be passed along to DirectShow filter supplied by a 3rd party MainConcept.

So, i the filter is a black box and ii I believe that the filter isn't deallocating media frames like it should be and iii Directshow filters must receive media frames allocated via the "COM-aware" CoTaskMemAlloc. Essentially, while I can allocate the frames, it's up to a 3rd party component to deallocate.

I want to be able to prove that the 3rd party component isn't deallocating properly. This is bad design. A thumb rule of good design is he who allocates, frees the resource.

Since the deallocation is in a different library your life isn't exactly a bed of roses. I would try to prove that the 3rd party library actually deallocates all frames, fire up WinDbg, put a breakpoint at CoTaskMemFree and wait to see if ever the break point is hit while I am inside the third party.

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.

The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta.