Original Message
>From: Shankar Unni
>Sent: 14 June 2005 18:10
> Igor Pechtchanski wrote:
>
>> Still cannot reproduce (my Process Explorer shows the same numbers as the
>> TaskManager). Which version of Process Explorer are you using?
>
> I can. I've just downloaded v9.11 for Win2K/XP/N
Igor Pechtchanski wrote:
Still cannot reproduce (my Process Explorer shows the same numbers as the
TaskManager). Which version of Process Explorer are you using?
I can. I've just downloaded v9.11 for Win2K/XP/NT 32-bit.
Anyway, it shows these wildly inflated Virtual Sizes for a lot of
appl
Original Message
>From: Brian Dessent
>Sent: 14 June 2005 03:23
> Procexp's "virtual size" column seems to be a meaningless number that
> procexp somehow arrives at.
It's the amount of reserved-but-not-yert-committed memory.
> It's not just cygwin processes that it
> seems to come up
Andrew DeFaria wrote:
> That may be but it does represent the "footprint" of the process or at
> least the amount of memory + swap reserved (doesn't it?). As such I seek
> to minimize such usage.
No, I don't think so. Taskman's "VM size" is what you are thinking of,
and is what procexp calls "pr
Igor Pechtchanski wrote:
On Tue, 14 Jun 2005, Alexey Fayans wrote:
All programs that use cygwin1.dll report very high virtual memory
usage. For example, bash from standard package report usage of
~420MB. Is it how it should be?
Hard to say without more information. Please see the Cygwin pro
Brian Dessent wrote:
Just to clarify:
taskman's "Mem usage" column == procexp's "Working set" column and
this is the amount of memory that is actually being used by the process.
taskman's "VM size" column == procexp's "Private bytes" column and
this is the total amount of code+data that has
Brian Dessent wrote:
> You're using process explorer, not task manager, and process explorer
> does not interact well with Cygwin for whatever reason. In this case it
> seems the procexp is computing the VM size wrong. If you use task
> manager and look at the "VM size" column it will be correct
Alexey Fayans wrote:
> Look at screenshot:
> http://home.shad.pp.ru/tmp/cygwin.png
You're using process explorer, not task manager, and process explorer
does not interact well with Cygwin for whatever reason. In this case it
seems the procexp is computing the VM size wrong. If you use task
mana
Igor Pechtchanski wrote:
On Mon, 13 Jun 2005, Alexey Fayans wrote:
All programs that use cygwin1.dll report very high virtual memory
usage. For example, bash from standard package report usage of
~420MB. Is it how it should be?
Hard to say without more information. Please see the Cygwin pro
On Mon, 13 Jun 2005, Alexey Fayans wrote:
> All programs that use cygwin1.dll report very high virtual memory usage.
> For example, bash from standard package report usage of ~420MB. Is it
> how it should be?
Hard to say without more information. Please see the Cygwin problem
reporting guideline
10 matches
Mail list logo
