--part1_c3.1bb3ac10.2964f870_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
A memory leak occurs when there is a logic bug in an application pgm that
actually uses more memory than needed (bug in the logic) and eventually you
run out of real and virtual memory from the OSystem. Like when a loging
program keeps everything in memory to make access faster.
There was a fix by Microsoft for at least for one leak in Windows NT back 2-3
yrs ago. But apps do their own thing most times. There does not have to be
a cpu loop to create a memory leak by an application, it is usually a logic
pblm trying to keep too much in memory at one time. When I am using Win2K ,
I can see exactly what is being used by program with the Windows Task Manager
and all the system tasks.
73 Mike N5MT
--part1_c3.1bb3ac10.2964f870_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
<HTML><FONT FACE=arial,helvetica><FONT SIZE=2 FAMILY="SANSSERIF" FACE="Arial"
LANG="0">A memory leak occurs when there is a logic bug in an application pgm
that actually uses more memory than needed (bug in the logic) and eventually
you run out of real and virtual memory from the OSystem. Like when a
loging program keeps everything in memory to make access faster.<BR>
<BR>
There was a fix by Microsoft for at least for one leak in Windows NT back 2-3
yrs ago. But apps do their own thing most times. There does not
have to be a cpu loop to create a memory leak by an application, it is usually
a logic pblm trying to keep too much in memory at one time. When I am
using Win2K , I can see exactly what is being used by program with the Windows
Task Manager and all the system tasks. <BR>
<BR>
73 Mike N5MT </FONT></HTML>
--part1_c3.1bb3ac10.2964f870_boundary--
|