0
0

One way of dealing with memory leaks


 invite response                
2018 May 1, 5:57pm   512 views  0 comments

by Patrick   ➕follow (55)   💰tip   ignore  

One of the biggest problems for low-level device programmers is keeping track of all the allocated memory so as to free it at the appropriate point. If some hardware device keeps allocating memory but fails to free it, eventually the device will crash, which is a major flaw. Normally. This case is an exception:

From: k...@rational.com (Kent Mitchell)
Subject: Re: Does memory leak?
Date: 1995/03/31
distribution: world
organization: Rational Software Corporation
newsgroups: comp.lang.ada

Norman H. Cohen (nco...@watson.ibm.com ) wrote:
: The only programs I know of with deliberate memory leaks are those whose
: executions are short enough, and whose target machines have enough
: virtual memory space, that running out of memory is not a concern.
: (This class of programs includes many student programming exercises and
: some simple applets and utilities; it includes few if any embedded or
: safety-critical programs.)

This sparked and interesting memory for me. I was once working with a
customer who was producing on-board software for a missile. In my analysis
of the code, I pointed out that they had a number of problems with storage
leaks. Imagine my surprise when the customers chief software engineer said
"Of course it leaks". He went on to point out that they had calculated the
amount of memory the application would leak in the total possible flight time
for the missile and then doubled that number. They added this much
additional memory to the hardware to "support" the leaks. Since the missile
will explode when it hits it's target or at the end of it's flight, the
ultimate in garbage collection is performed without programmer intervention.
no comments found

Please register to comment:

api   best comments   contact   latest images   memes   one year ago   random   suggestions