Brad Fitzpatrick (brad) wrote,
Brad Fitzpatrick
brad

perl leaks lame

Debugging leaks in Perl code sucks.

Perlbal recently, somewhere, is leaking ClientProxy objects. I keep track of when they're made, and when they're destroyed, and I know how many objects of each type are in memory at a time.... for ClientProxy it goes up and down, but mostly up. (all that infrastructure went in earlier when I worked with whitaker on tracing a prior Perlbal leak)

So now I know there's a leak, but hell if I can find it.

And all the leak detection modules out there either:

-- require -DDEBUGGING, not enabled on our production debian servers
-- require normal control flow (not event loop)
-- don't find references embedded in closures: $foo has member 'bar' which is sub { my $baz = \$foo; }

So basically it's just a lot of hunting and binary searching through changesets at this point.

YAY

want sleep

props to xb95 for joining me in pain, though.
Tags: perl, tech
Subscribe
  • Post a new comment

    Error

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 5 comments