SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Computer Learning

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: thecow who wrote (14725)1/10/2001 9:41:56 AM
From: PMS Witch  Read Replies (2) of 110652
 
Memory leaks ...

A project I was working on was suffering from not returning memory to the system when it finished using it. Couple this with the old data remaining, and being accessed when it was no longer in allocated memory, and I had a real buggy mess. I wrote container routines around all memory routine calls to track their activity to a log file. Processing the log was a trivial matter, and I was directed to those parts of my project that were the cause of the trouble.

But this was a time consuming piece of work. And after the thing was fixed, I needed to remove the extra code.

The point I'm trying to make is that it is possible for developers to address the memory leak issue, but it takes extra time and effort, and the temptation to skip this work, especially when working to meet deadline and budget restrictions, is almost irresistible.

Cheers, PW.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext