use Perl

Tracking down memory leaks is no fun and frankly, our application is leaking like a stuck pig. In the process of trying to track all of this down, I wrote and submitted a little change for Devel::Object::Leak. This change lets you add callbacks to a global bless. So right now I want to know where my schema objects are being created:

package leaks;

use Data::Dumper::Simple;
$Data::Dumper::Indent   = 1;
$Data::Dumper::Sortkeys = 1;

use Devel::Leak::Object GLOBAL_bless => sub {
    my ($reference, $class) = @_;
    return unless $class && $class->isa('Pips3::Schema');
    my ($package, $file, $line) = caller(2);

    warn Dumper($package, $file, $line, $class);
    warn $/;
};

1;

And then I run a test:

perl -Mleaks t/acceptance.t t/acceptance/import/import_id.yml

Then I get a handy list of where all of those things are getting instantiated (trimmed for clarity):

$package = 'DBIx::Class::Schema';
$file = '...deps/lib/perl5//DBIx/Class/Schema.pm';
$line = 707;
$class = 'Pips3::Schema';

$package = 'DBIx::Class::Schema';
$file = '...deps/lib/perl5//DBIx/Class/Schema.pm';
$line = 589;
$class = 'Pips3::Schema';

$package = 'Catalyst::Model::DBIC::Schema';
$file = '...deps/lib/perl5//Catalyst/Model/DBIC/Schema.pm';
$line = 288;
$class = 'Pips3::Schema';

Well, that told me some of what I needed to know, but not enough. However now that I can add callbacks to bless, I can dump stack traces and really figure out what's going on.

(What's really interesting is the discovery that there are three schema objects being created here, when I thought there should only be only or two).