Well, there wasn't a problem with DBI at all.
Problem was (and still is, actually) that I had a reference loop. The
objects in question wouldn't be freed until *all* the object's went out of
scope. This was at the end of the program due to the reference loop. I
stuck in some code to break the loop, and *poof*, no more memory leak.
Funny how that works. BTW, the reference loops are intentional, in that
line item objects all point to their header, and visa-versa. Makes coding
very simple, but it adds a few gotchas.
I did learn how to use Devel::Leak, however, so it wasn't a complete waste.
I take it that weak references are a 5.6.x thing, and are not available with
5.005_03? If so, I'll have to live with having a method which breaks the
loop manually. Ah well.
Thanks for your help Tim. It was a learning experience.
-klm.
-------Original Message-----
--From: Ken Miller [mailto:[EMAIL PROTECTED]]
--Sent: Thursday, February 28, 2002 7:18 AM
--To: Tim Bunce; [EMAIL PROTECTED]
--Subject: RE: Leaking SV's with DBI - how to find where?
--
--
--I'm going to give these suggestions a try to try and narrow this down.
--
--Stay tuned.
--
-- -klm.
--
