OpenEuphoria

ODBC.ew

• Posted by Michael J. Sabal <m_sabal at ??hoo.com> Oct 11, 2007
• 601 views

Matt,
  I'm curious as to why you implemented freeStmt the way you did.  As you may
recall, I've had a serious memory leak when using the standard sequence of
prepareSQL, executeSQL, getData, freeStmt.  I'm using v. 1.34, and I only 
finally noticed that freeStmt does not use the ODBC function.  All the calls
to free() are in Euphoria, where the allocation was done in the dll.  I've
elected to change my methodology to execDirectODBC; although I won't be able
to test it until later this afternoon.

  Just for background - when running the program for 24 hours without
remediation, memory usage is in excess of 800MB.  When cleaning up and re-
initializing the ODBC connection once an hour, memory usage runs about 150MB 
for 24 hours.  When stopping the service and restarting it, memory usage 
is 8MB.  My goal is to keep the program at a constant rate over a full week,
expected to be in the neighborhood of 30MB.

  Any insight would be appreciated.

Michael J. Sabal