44. Memory Leak : C

Memory Leak

It is a toxin for programming since programming shows indistinct conduct because of the memory spill. It happens when we make a memory in a load and neglect to erase it. It happens when we don't utilize dynamic memory appropriately. On the off chance that the framework has sufficient memory, that case additionally dials back the exhibition of the framework. To stay away from this issue, memory designated on the load ought to consistently be liberated when not required. 

Purposes behind Memory spill - 

• We don't free the memory that is not generally required. 
• We do attempt to free the memory, yet we don't have the reference to a hanging pointer. 
• We attempt to free the memory utilizing some unacceptable capacity. 

How to keep away from memory spill in C? 

To keep away from memory spills, we ought to consistently be liberated from the memory distributed on the stack when presently not required. In circumstances where dynamic distribution is not generally needed to keep up with, let loose space before the program ends. 

Two principles ought to be noticed for any C program identified with dynamic memory the board are - 

• Any memory that is powerfully saved with malloc, calloc, or realloc should be deallocated through utilizing free(). 
• At the point when the program executes its last guidance and has dynamic memory impedes that is not deallocated, it is viewed as inaccurate.