Skip Menu |

This queue is for tickets about the Template-Alloy CPAN distribution.

Report information
The Basics
Id: 30430
Status: resolved
Priority: 0/
Queue: Template-Alloy

People
Owner: Nobody in particular
Requestors: cpan [...] fireartist.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 1.008
Fixed in: (no value)



Subject: memory leak (circular reference)
I'm tracking down memory leaks in a persistent fastcgi app, and came across this. Dumping the object with Data::Dumper shows: (irrelevant lines removed) $VAR1 = bless( { 'INCLUDE_PATH' => [ '/path2', '/path1' ], 'INCLUDE_PATHS' => $VAR1->{'INCLUDE_PATH'} }, 'Template::Alloy' ); I think rather than using weaken(), simply adding the following line to the include_paths() subroutine in Template/Alloy.pm would probably be best. It should be inserted before $paths is returned in line 781. $paths = [@$paths] if UNIVERSAL::isa($paths, 'ARRAY');
On Fri Nov 02 10:33:46 2007, CFRANKS wrote: Show quoted text
> I'm tracking down memory leaks in a persistent fastcgi app, and came > across this.
Sorry, I should have tested this before posting... I've made the change, but the leak's still being reported. I'll try tracking it down again.
I would be interested in seeing the application setup for this FCGI that is causing the issue. I'd like to see the parameters that are getting passed to Template::Alloy that might be causing it to go into a circular ref structure. I was pretty sure we'd kept things clean.
As I haven't seen anything on this thread in a year - and i haven't been able to duplicate the issue, I'm marking it as resolved.