On Thu, 14 Oct 1999 Matthew Wakeling wrote: > Don't dismiss memory leaks so easily. It's fine for a program to use a lot > of RAM. However, if a program allocates the RAM and forgets to deallocate > it, that points at a fairly serious bug. The equivalent opposite bug > (deallocating without allocating) is bad enough to cause a guru on the > spot. On my system MD-2 has had serious memory management problems, including severe leaks, since the earliest version I tried (0.198 beta). I suspect that these problems are not unique to me. Try this: - Go to a newsgroup which contains many large multi-part binary postings. - For a posting which is in multiple parts, select several parts not including the first. Use the Message/Download menu item to download the bodies of these messages. - Double-click on one of the just-downloaded posts in the list window. Eventually the article read window will appear (filled with uuencoded data of course). - Close the read article window. Note that you now have a couple of hundred K or so less free memory. - You can repeat this article viewing as many times as you like, each time a large amount of memory is lost. It is not returned when you quit MD-2. For further examination, you can run a utility like SFragMem beforehand to see where the "leaked" memory is. -- Mark ________________________________________________________________ MicroDot-II Mailing List - Info & Archive: http://www.vapor.com/ For Listserver Help: <[EMAIL PROTECTED]>, "HELP" To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
