Let's disambiguate technically:
1. A process uses a lot of memory beyond the capacity of the OS. this is a design issue.
2. When a process is ended, the OS will claim back all resources recorded in the process table. If not, this process must trespass resource it doesn't own. The bucket leaks something to the floor.
3. The OS or the process itself can always track what it posses by checking the process table.
As far as I know in our team, C++ engineers only claim leakages found when the process ended. When the process is not ended, it is access violation/ segment fault etc.
【 在 Peppy (幸福万岁~~~) 的大作中提到: 】
: Memory leakage is the program lost track of the memories it requested along
: the time... such that some memory is allocated to the program in operating s
: ystem's record, however, program cannot access it.
提示: 本博文来自于 Programming 版