Error - template LAYOUT-DATA-WRAPPER not found

A configuration error was detected in the CGI script; the LAYOUT-DATA-WRAPPER template could not be found.

Error - template STYLE-SHEET not found

A configuration error was detected in the CGI script; the STYLE-SHEET template could not be found.

Error - template SUB-TOP-BANNER not found

A configuration error was detected in the CGI script; the SUB-TOP-BANNER template could not be found.

Subject:	Re: ram
From:	Joe Pearson <[log in to unmask]>
Reply To:	PCSOFT - PC software discussion list <[log in to unmask]>
Date:	Fri, 13 Feb 1998 14:55:27 +0200
Content-Type:	text/plain
Parts/Attachments:	text/plain (30 lines)

Can someone explain memory leaks in non-programmer's terms?  I
understand that they are basically blocks or buffers requested by the
application at start-up or while running, but not released when it
closes.

What I can't understand is why the operating system ... or a clever
utility from one of those clever programmers out there ... can't simply
identify bits if memory whose "owning" module has gone away and free
them (without needing a re-boot).

I'm seeing memory space like disk space, where clusters can be marked as
in use but not part of any file.  Is this just too simplistic?


Joe Pearson
Dimension Data Consulting
Johannesburg
South Africa
Direct: +27 11 709 1112   Mobile: +27 83 454 6033
[log in to unmask]




>


          PCSOFT:  http://nospin.com  or  [log in to unmask]

ATOM RSS1 RSS2

LISTSERV.ICORS.ORG