WriteLog
[Top] [All Lists]

[WriteLog] Software Memory Leak

To: <writelog@contesting.com>
Subject: [WriteLog] Software Memory Leak
From: umina@theuminas.com (Len Umina)
Date: Wed, 2 Jan 2002 18:09:14 -0800
This is a multi-part message in MIME format.

------=_NextPart_000_0190_01C193B8.965198C0
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: 7bit

Mike,

It's not the fact that the program uses or reserves more than need or that
it keeps everything in memory to make the program run faster that causes the
leak.

The leak is caused by the programmer or the operating system inadvertently
forgetting to free up the memory that was reserved or used by the program.

73, Len K1LU (a experienced memory leaker)
  -----Original Message-----
  From: writelog-admin@contesting.com
[mailto:writelog-admin@contesting.com]On Behalf Of N5MT@aol.com
  Sent: Wednesday, January 02, 2002 3:58 PM
  To: jflanders2@home.com
  Cc: writelog@contesting.com
  Subject: [WriteLog] Software Memory Leak


  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

------=_NextPart_000_0190_01C193B8.965198C0
Content-Type: text/html;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2712.300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D234250102-03012002><FONT face=3DArial color=3D#0000ff =

size=3D2>Mike,</FONT></SPAN></DIV>
<DIV><SPAN class=3D234250102-03012002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D234250102-03012002><FONT face=3DArial color=3D#0000ff =
size=3D2>It's=20
not the fact that the program uses or reserves more than need or that it =
keeps=20
everything in memory to make the program run faster that causes the=20
leak.</FONT></SPAN></DIV>
<DIV><SPAN class=3D234250102-03012002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D234250102-03012002><FONT face=3DArial color=3D#0000ff =
size=3D2>The=20
leak is caused by the programmer or the operating system inadvertently=20
forgetting to free up the memory that was reserved or used by the=20
program.</FONT></SPAN></DIV>
<DIV><SPAN class=3D234250102-03012002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D234250102-03012002><FONT face=3DArial color=3D#0000ff =
size=3D2>73,=20
Len K1LU (a experienced memory leaker)</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B>=20
  writelog-admin@contesting.com =
[mailto:writelog-admin@contesting.com]<B>On=20
  Behalf Of </B>N5MT@aol.com<BR><B>Sent:</B> Wednesday, January 02, 2002 =
3:58=20
  PM<BR><B>To:</B> jflanders2@home.com<BR><B>Cc:</B>=20
  writelog@contesting.com<BR><B>Subject:</B> [WriteLog] Software Memory=20
  Leak<BR><BR></FONT></DIV><FONT face=3Darial,helvetica><FONT lang=3D0 =
face=3DArial=20
  size=3D2 FAMILY=3D"SANSSERIF">A memory leak occurs when there is a =
logic bug in an=20
  application pgm that actually uses more memory than needed (bug in the =
logic)=20
  and eventually you run out of real and virtual memory from the =
OSystem.&nbsp;=20
  Like when a loging program keeps everything in memory to make access=20
  faster.<BR><BR>There was a fix by Microsoft for at least for one leak =
in=20
  Windows NT back 2-3 yrs ago.&nbsp; But apps do their own thing most=20
  times.&nbsp; There does not have to be a cpu loop to create a memory =
leak by=20
  an application, it is usually a logic pblm trying to keep too much in =
memory=20
  at one time.&nbsp; When I am using Win2K , I can see exactly what is =
being=20
  used by program with the Windows Task Manager and all the system =
tasks.=20
  <BR><BR>73&nbsp; Mike&nbsp; N5MT&nbsp; =
</FONT></FONT></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0190_01C193B8.965198C0--



<Prev in Thread] Current Thread [Next in Thread>