Цитата berkut_0:
На скриншоте выше, что я прикладывал, есть System Commit - 10.0 GB, и Physical Memory - 5.6 GB
10.0 != 5.6 »
|
Commit - это сколько на данный момент запрошено (сумма колонки private bytes на главной странице process explorer) всеми запущенными процессами, а не сколько занято реально.
Цитата:
Private Bytes refer to the amount of memory that the process executable has asked for - not necessarily the amount it is actually using. They are "private" because they (usually) exclude memory-mapped files (i.e. shared DLLs). But - here's the catch - they don't necessarily exclude memory allocated by those files. There is no way to tell whether a change in private bytes was due to the executable itself, or due to a linked library. Private bytes are also not exclusively physical memory; they can be paged to disk or in the standby page list (i.e. no longer in use, but not paged yet either).
Working Set refers to the total physical memory (RAM) used by the process. However, unlike private bytes, this also includes memory-mapped files and various other resources, so it's an even less accurate measurement than the private bytes. This is the same value that gets reported in Task Manager's "Mem Usage" and has been the source of endless amounts of confusion in recent years. Memory in the Working Set is "physical" in the sense that it can be addressed without a page fault; however, the standby page list is also still physically in memory but not reported in the Working Set, and this is why you might see the "Mem Usage" suddenly drop when you minimize an application.
|
Цитата berkut_0:
|
Это всё ради эксперимента »
|
Уверяю, ни к чему хорошему эти эксперименты не приведут. Ситуацию с утечкой точно не решат.
