Re: memory leak in ora73.dll

To startwith, if you feel you have memory leaks, call up support and get them to ship you the latest RSF (which includes ORA73.DLL).

Secondly, note that most of these memory leak detection tools do not always tell the truth. Or, I should say, they leave the final deduction upto the user (whether it is a leak or not). For e.g., a malloc(), when not matched with a free() will be reported as a leak. Well, there are cases, when the software developer intentionally does not perform the free as it expects the free to happen at app close time. This technique is typically used for performance reasons, especially when the memory blocks are small.

Anycase, call up support and email them your memory leak report. Ignore the leaks that are reported at app close time. The only memory leaks of concern should be the ones which happen when the app is in operation, as that will determine the amount of time the server can remain up (before the memory runs out).

-sm

On Fri, 26 Sep 1997 11:45:52 -0700, Phil Tsao <philt_at_technologist.com> wrote:

>We do development using VC++, and Oracle's ODBC 2.x driver.
>What we found out recently is that ora73.dll has serious memory leak
>problem (we use Purify to monitor ).
>I was wondering if anyone encounter the same problem.
>Any feedback would be very appreciated.
>
>--
>Phil Tsao
>e-mail: philt_at_technologist.com
>
>
>
Received on Thu Oct 02 1997 - 00:00:00 CDT