What is Memory Leak?

Memory leak happens when the programmer make a memory in stack and then don’t delete it. This is major issues for the program like daemons or servers, which never terminates. To maintain a strategic distance from memory leak, memory assigned on stack ought to dependably be liberated when didn’t really required. To find a memory leak, we can have following procedures:
Discover the memory leak – Detect the presence of memory leak in the framework, given a specific reproducible sequence. We ought to have the ability to distinguish a particular procedure.
Separate the memory leak – Determine the correct area in the source code where the un–freed allotment happens. This could be an extensive or monotonous process, requiring particular tool, trial–and–error, and cooperation with the first creator of the code.
Remove the memory leak – After the initial two stages are finished, this is simple. Settling the memory leak for the most part includes adding some code to free the memory in the code path.