After the process finishes, all memory for the process is freed, including memory leaks on the heap.

After the process finishes, all memory for the process is freed, including memory leaks on the heap. The reason is that when the process is finished, the GDT, LDT, and page directories are changed by the operating system, the logical memory is all gone, the contents of the physical memory may still be in but the logical memory has been removed from the LDT and GDT, the page directory table is all destroyed, so the memory will be fully recovered.

This code, I personally think that can be used as an example, not to please more advice:

[C-sharp]View Plaincopy

2. #include <cstdlib>
4. using namespace Std;
6. const static int const_once = 1024*1024*2;
8. int _tmain (int argc, _tchar* argv[])
10. {
12. int *a;
14. for (int cnt=0;cnt<=10;cnt++)
16. {
18. A = new int[const_once];
20. A[10] = 1;
22. A[CONST_ONCE-10] = 1;
24. }
26. System ("pause");
28. Exit (0);
30. return 0;
32. }

Operation Result:

When you pause:

After:

I this program does not account for hundreds of trillion memory, you can try repeatedly, some people always say that memory leaks until the new start to be recycled, I think this is the DOS ERA, DOS there is no paging fragmented virtual storage of these management, so it will always leak it.

Transferred from: http://blog.csdn.net/x50573750/article/details/6171604

After the process finishes, all memory for the process is freed, including memory leaks on the heap.