sql anywhere memory leak

[cmchang]

We have a test case showing large memory leaks from the odbc-driver for
sqlAnywhere. Where/whom to contact to get this fixed.

thanks,

-Carlos

[Jim Kissel]

Try ri...@watcom.com
He may not be the correct person, but he will pass it on
to someone who may be able to help.

On Mon, 21 Apr 1997 14:28:57 -0700, cmchang <cmc...@ix.netcom.com>
wrote:

[Ian Knowles]

cmchang <cmc...@ix.netcom.com> wrote:

Carlos,

>We have a test case showing large memory leaks from the odbc-driver for
>sqlAnywhere.

Can you repeat this test using a simple tool such as MSQuery or by
using the ODBC developer's kit test app?

If so I would be interested to study the case as I am also suspicious
that such a leak may well exist, but have only so far seen symptoms
(such as the "not enough memory to run" message) after starting up and
shutting down a very large application numerous times (ie. could in
fact be due a problem elsewhere in the app.).

If you are experiencing the "not enough memory" message I would be
suspecting the inappropriate usage of "fixed" data segments (although
they can be necessary for some drivers they are often used accidently
due to an incorrect or missing .DEF file). The "not enough memory"
message is usually actually referring to an inability to allocate
memory below the 1Meg line (and I thought that crap had disappeared
with DOS..). Using DLL's with such "fixed" data segments can cause
extra fragmentation below the 1Meg line and lead to the "not enough
memory" problem.

I have found that the "HeapWalker" tool can be invaluable in
diagnosing this sort of condition (unfortunately every time I attempt
to run it with the application I am developing it decides to GP...).

> Where/whom to contact to get this fixed.

I would be contacting Sybase (you could start with their Web page
http://www.sybase.com).

In fact if you can convince me I'll be more than glad to contact them
for you!

Regards,

Ian Knowles (remove the .nospam to reply)