I have a very long running Perl process. I recently upgraded the DBI from 1.32 to 1.33 (and then 1.34) and now, the process is leaking memory. Given the complexity of the project, it's not possible to reduce it to a simple test case at this time, but it's definitely related to the DBI -- if I downgrade to 1.32, the problem goes away.
Has anyone else seen this? I'm using the DBD::mysql drivers (the latest, just released the other day). I'm wondering if anything has changed in the internal structures that might prevent objects from being GC'd (the DBI connection is being used in a wrapper, non-subclassing module) or if this is a C issue. Philip * Philip Molter * Texas.net Internet * http://www.texas.net/ * [EMAIL PROTECTED]
