What is memory leakage in OOPS concept and what is the best way to cutdown it???
Answer I do not think memory leaks are restricted to OOP. They are not confined to OOP, any style of programming can have memory leaks. A lot of OOP is concerned with concepts rather than low level details. It is at the low level details of specific languages and their memory management model and how they are used (or abused) that memory leaks occur. A memory leak is a situation where a program obtains memory and fails to return it when finished with it, i.e. a program allocates memory and fails to release it. Small one off memory leaks are not that important. Large memory leaks will obviously be more worrisome. Repeated memory leaks are the worst, especially in long running applications such as servers, where even a small memory leak repeated frequently will over time cause more and more memory to be allocated by the program. Eventually the process and quite probably the system as a whole will run out of memory, at which point it is likely to require re-starting (or re-booting the who
