Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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.

Technology Stocks : BORL: Time to BUY! -- Ignore unavailable to you. Want to Upgrade?

To: Bill Tucker who wrote (9804)	4/9/1998 8:15:00 AM
From: John Solder	Respond to of 10836

Basically a memory leak is when a program allocates memory in normal operation but never frees the memory when finished with it. This causes a net loss of available memory space to that program and all other programs running on that computer. e.g. A program allocates memory for group of classes and stores pointers to the classes in a vector, if the vector is destroyed but the memory for the class instances is not specifically freed that memory is essentially lost. This is not usually a problem for programs that start and stop because allocated memory is freed when the program dies, but the in the example of an RDBMS that runs continually, the problem can be terrible. The solution is to run something like Purify on your programs to check for such conditions. I have not heard about leaks from BORL products but would not be too surprised. Leaks generally indicate code not was rushed out and not fully tested.