Re: how do you terminate an application?

I would expect the Task Manager to show some nominally useful figures

Great. Come back when you're sure.

MarkH

"Michael B. Johnson" <mjohnson@xxxxxxxxxxx> wrote in message
news:v09qu1limbdajjbt47ndrf19b3b2j08rsv@xxxxxxxxxx
On Fri, 10 Feb 2006 19:01:02 -0000, "Mark Hurst" <markh@ NOTTHISBIT
keysound.com> wrote:

developer tools installed I might be tempted to play. However I do
remember
that DLLs run in-process, and also that 'End' kills the process. I am
rusty
on 32-bit Windows but I would speculate that malloc's heap is in the
process
and so dies with it. Okay, maybe I'm wrong and I will have to stick to

Probably so, since that was the design intent of Win32 - to separate
application
memory space to make them more reliable. I wonder what happens about
out-of-process Active-X Executable calls, though? With COM reference
counting,
those would probably also be dealt with. But then those apps just might
hang
around, like MS Word does when my automation macros fail and my VB app
ends. I
rather suspect that in theory everything should happen in practice as it
does in
theory, but that in practice they may not.

So, get the developer tools, install them and find out why so many oppose
band-aiding obscure code by using an END statement as opposed to releasing
resources in a logic controlled and systematic way. After all, why spend
everyone's time when you could be doing some valuable research to satisfy
your
curiousity and add to your understanding?

raising my doubts for now. Here's another one: are you *sure* that
watching
Task Manager is a reliable way of monitoring memory consumption in
real-time? From old experiments with System Monitor I seem to remember
that
this figure doesn't show what it appears to show.

I would expect the Task Manager to show some nominally useful figures:
consider
a border-line case where almost all physical RAM is used up. Allocating
additional RAM would probably cause paging to the hard disk. Therefore, if
Task
Manager shows that memory isn't apparently released, other applications'
(responsiveness) will probably be at least indirectly affected.

If you don't trust Task Manager, perhaps Performance Monitor may be of
some
help?
_______________________
Michael B. Johnson


.

Relevant Pages

  • Re: Terminal Server 32bit /PAE vs 64bit
    ... memory usage goes back to about 3.5gb. ... Provision Networks VIP ... monitor does not see it with all my processes running. ... the best way to monitor this stuff as I have seen thru the task manager ...
    (microsoft.public.windows.terminal_services)
  • Re: how do you terminate an application?
    ... memory space to make them more reliable. ... I would expect the Task Manager to show some nominally useful figures: ... a border-line case where almost all physical RAM is used up. ... If you don't trust Task Manager, perhaps Performance Monitor may be of some ...
    (comp.lang.basic.visual.misc)
  • Re: Allocated Memory Alert on SBS
    ... Task Manager. ... Monitor the activity of these resources over a few days. ... they continue to use a high level of memory and are less critical processes ... You can disable this alert or change its threshold by using the Change Alert ...
    (microsoft.public.windows.server.sbs)
  • allocated memory alert
    ... Consistently high memory usage can cause performance problems. ... memory, use Task Manager. ... Monitor the activity of these resources over a few ...
    (microsoft.public.windows.server.sbs)
  • Re: Memory usage f95...
    ... Task Manager shows that 500Mb has been set aside in Virtual Memory. ... Virtual Memory, not physical RAM. ...
    (comp.lang.fortran)