On Thu, Dec 20, 2001 at 09:23:02AM -0500, Hardy Merrill wrote: : I'm curious about this now - it would seem that Rudy is right, : that when the hashref scalar gets assigned the reference to the : "new" hash, then the only existing reference to the old hash : should disappear, which should in theory(?) make the memory : taken by that old hash available again via garbage collection, : right? Why isn't this happening? : : Tim, or anyone else know the answer?
Two bits of information are still missing. What DBD is the problem happening under? What's the code look like (post an example)? I would think that if the DBI had a massive memory leak (30MB), there would be many more complaints. My guess would be either a bad driver or somehow, that returned hashref is being used in such a way that it isn't garbage collection (stuck in an array, put in an object, etc.) * Philip Molter * Texas.net Internet * http://www.texas.net/ * [EMAIL PROTECTED]
