Write a program (with the programming language and on the platform of your choice) to demonstrate the memory leak problem. The full program and the program outputs should be included at the end of the report as an appendix.

If you write the program on a platform which has built-in garbage collection mechanism, special care has to be taken to introduce the memory leak problem.

Execute the program until it cannot proceed anymore. You may have to allocate big chunks of memory iteratively to reach to this point quickly. This is even more so if you are running the program on a 64-bit operating system. Based on your observation and your understanding of the principles of a paging memory management system, answer the following questions:

A. How much memory has the program used when reaching the point where it cannot proceed anymore? What is the physical (32-bit or 64-bit) and logical address space of the computer you run this application on? What is the size of the physical memory (RAM) of the computer you run this application on?

B. What type of memory, virtual or physical, is exhausted when there is a memory leak problem with a process?

C. When a process that has a memory leak problem cannot proceed anymore, does it prevent any other program from starting/running due to lack of memory? Does it slow down the whole system?

D. On a platform which has built-in garbage collection mechanism, e.g., .NET and JVM, to a large extent, the memory leak problem can be avoided. Why?