in reply to Re^2: Detecting memory leaks.
in thread Detecting memory leaks.

But even so, the variable should be destroyed when it moves out of scope and it is not, so I suspect some sort of circular reference. I just can't see it.

If $booking_dlg->{booking_main} contains a reference to $booking_dlg? Then this is a circular reference:

$booking_dlg->{Ctl_Booking_Referring_Doctor_Txt} = i_staticText->new($
+booking_dlg->{booking_main}

[download]
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". I'm with torvalds on this
In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked

Replies are listed 'Best First'.
Re^4: Detecting memory leaks.
by Steve_BZ (Chaplain) on May 04, 2015 at 16:53 UTC

    Oh, for a minute I got my hopes up!

    I did: 

    
    $mu->record('at i_Booking exit');
    
    $mu->dump();
            
    
    print "Find cycle >>>>>>>>";
    find_cycle($booking_dlg);
    print "<<<<<<<<<< Find cycle";
    
    return $booking_dlg;

    [download]

    And the 

        find_cycle($booking_dlg);

    [download]

    Did nothing.

    Oh Well.

    Regards

    Steve.

[reply]
[d/l]
[select]
[reply]

        Hi Anon,

        I'm looking at the synopsis for Devel::Leak, 

        use Devel::Leak;
... setup code
 
my $count = Devel::Leak::NoteSV($handle);
 
... code that may leak
 
Devel::Leak::CheckSV($handle);

        [download]

        What is $handle

        Regards

        Steve

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom