I haven't had reports of leaks, and it's entirely possible. It is probably NOT the DBI itself, more likely it is DBD::ODBC or the ODBC Driver itself. I could have a few perl buffers being allocated that I think should be destroyed, but are not.
Can you estimate any metrics? I.e. 5K/hour over 500 select statements or something similar? Is your script being called, then it exits, then it's called again? If so, I'd look at the calling program, if someone wrote that. We had a script under NT once that called CreateProcess directly and, if I recall correctly, TWO handles need to be freed after executing, both in the PROCESS_INFORMATION structure. Regards, Jeff P.S. do you always write in such a tiny font? 8pt is *killing* my eyes. -----Original Message----- From: Gary Gauthier [mailto:[EMAIL PROTECTED]] Sent: Friday, July 26, 2002 8:36 AM To: [EMAIL PROTECTED] Cc: > Subject: Possibility of a Memory Leak in DBI or DBD-ODBC Jeff; I'm using DBI v1.30 and DBD-ODBC v0.43. My database app is invoked about 40,000 times over the course of about 2 days to generate test scripts for some automated test equipment. I've been noticing the memory usage creeping up slowly over the course of the runs. While I can't be absolutely sure it's the driver, I have seen a report on the developers mail list regarding this problem in recent versions. Have you done any tests to check for leaks, or have you had any reports of leaks? Regards; Gary
