[WriteLog] Software Memory Leak
Marijan Miletic, S56A
artinian@siol.net
Thu, 3 Jan 2002 12:39:55 -0000
This is a multi-part message in MIME format.
------=_NextPart_000_002B_01C19453.BF8C8BA0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
This problem was called "garbage collection" in the previous millenium :-)
73 de Mario, S56A, N1YU
----- Original Message -----
From: Len Umina
To: N5MT@aol.com ; jflanders2@home.com
Cc: writelog@contesting.com
Sent: Thursday, January 03, 2002 2:09 AM
Subject: RE: [WriteLog] Software Memory Leak
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_002B_01C19453.BF8C8BA0
Content-Type: text/html;
charset="iso-8859-1"
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=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>This problem was called "garbage =
collection"=20
in the previous millenium :-)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>73 de Mario, S56A, N1YU</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Dumina@theuminas.com href=3D"mailto:umina@theuminas.com">Len =
Umina</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3DN5MT@aol.com=20
href=3D"mailto:N5MT@aol.com">N5MT@aol.com</A> ; <A =
title=3Djflanders2@home.com=20
href=3D"mailto:jflanders2@home.com">jflanders2@home.com</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Dwritelog@contesting.com=20
href=3D"mailto:writelog@contesting.com">writelog@contesting.com</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, January 03, =
2002 2:09=20
AM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [WriteLog] =
Software Memory=20
Leak</DIV>
<DIV><BR></DIV>
<DIV><SPAN class=3D234250102-03012002><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Mike,</FONT></SPAN></DIV>
<DIV><SPAN class=3D234250102-03012002><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </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=20
size=3D2></FONT></SPAN> </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 =
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=20
size=3D2></FONT></SPAN> </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> <A=20
=
href=3D"mailto:writelog-admin@contesting.com">writelog-admin@contesting.c=
om</A>=20
[mailto:writelog-admin@contesting.com]<B>On Behalf Of </B><A=20
href=3D"mailto:N5MT@aol.com">N5MT@aol.com</A><BR><B>Sent:</B> =
Wednesday,=20
January 02, 2002 3:58 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=20
an application pgm that actually uses more memory than needed (bug =
in the=20
logic) and eventually you run out of real and virtual memory from =
the=20
OSystem. Like when a loging program keeps everything in memory =
to make=20
access faster.<BR><BR>There was a fix by Microsoft for at least for =
one leak=20
in Windows NT back 2-3 yrs ago. But apps do their own thing =
most=20
times. 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. 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 Mike N5MT =20
</FONT></FONT></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_002B_01C19453.BF8C8BA0--