how detect memory leaks

Finding memory leaks is difficult. The basic nature of the problem is that how can you tell if the process is done with a piece of memory that has been allocated. This is the magic of memory managers in C# and Java (which have the benefit of IL and Javabyte code respectively). The garbage collector makes a determination about whether a variable has gone out of scope and deallocates/frees that memory. There are a lot of tools to help you determine that from your code. Here is a link to one of them:

http://deleaker.com/

Without the source code, it would be difficult to analyze. I hope this helps.

MFC already contains a memory leak detection mechanism. Visual studio generates a couple of header lines in your code that replace in DEBUG builds the calls to the new operator with a call to a debug-new function, which records every single memory allocation and the place it comes from. At the end of the run, when all allocations made by new should have been given back by a corresponding call to delete, MFC outputs a list in the output window of all those allocations that are still open.

This is not the most sophisticated memory leak tracker, but it works quite well in many situations. Just learn to interpret that list and you get quite a long way.

You can use visual leak detector in link
https://vld.codeplex.com/[^]

This is not a Good Question, try to Google. Please FAQ read before post a any type of question Code Project Quick Answers FAQ[^]

There is no direct way of identifying memory leaks, even if there are tools available it is very little that they can do for you.Best is follow this approach
Launch Process Explorer and montior "Private Bytes", "Handles" for your process.
Now start executing the use cases which gives you memory leak.Now observe what is growing if Private Bytes is growing then you have allocated memory using new or malloc but not yet released.
If handle count is going up then you have not released certain handles.
Just look into that area of code and fix the problem.