Why do many programs not release memory when closed?

[Beemer]

What is the reason that some programs do not release memory after they are
closed in XP SP2? Task Manager shows them still running as processes.
These are applications e.g. Acrobat or Newsreaders not Anti-Virus or defrag
programs.

regards

Beemer

 

[Beemer]

What is the reason that some programs do not release memory after they are
closed in XP SP2? Task Manager shows them still running as processes.
These are applications e.g. Acrobat or Newsreaders not Anti-Virus or
defrag programs.

regards

Beemer

I should have added that even MS Outlook does this.

Beemer

 

[Singapore Web Design]

Hello,

Not normal - unless the program is configured to run in the background.
Outlook may be running in the background with an icon in the system tray.
Acrobat reader_sl.exe is used to speed load acrobat reader itself.

--
Singapore Web Design
http://www.bootstrike.com/Webdesign/
Singapore Web Hosting
http://www.bootstrike.com/WinXP/faq.html
Windows XP FAQ

 

[Gerry]

Task Manager shows allocations not usage, You can encounter programmes
that do not release memory but they are not that common as such users
think. These are generally referred to as "memory leaks". They are
caused by poor programming. There have been suspicions about Adobe
Acrobat Reader in the past. Memory leaks are one reason for not leaving
computers on 24/7.

http://aumha.org/win5/a/xpvm.htm

http://en.wikipedia.org/wiki/Memory_leak

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[John John]

What is the reason that some programs do not release memory after they are
closed in XP SP2? Task Manager shows them still running as processes.
These are applications e.g. Acrobat or Newsreaders not Anti-Virus or defrag
programs.

Plain and simple, because they are poorly written applications!

John

 

[NoConsequence]

Plain and simple, because they are poorly written applications!

John

Exactly.

When learning to write apps, we are taught that when you are done with
a resource you should release it, thereby releasing the resources it
was holding onto. The programming compliler should take care of it,
but you shouldn't count on that. I always release all my resources
when the app doesn't need it anymore.