in reply to Re^2: Losing my memory
in thread Losing my memory

There's an awful lot of problems with that post which you should fix up.

— Ken

Replies are listed 'Best First'.
Re^4: Losing my memory
by nzsvz9 (Sexton) on Feb 09, 2021 at 06:44 UTC
    Ken and all who posted,

    I wanted to post what eventually worked - a combination of several items put forward.

    Creating the initial Photo image with no reference, then immediately loading the image from the file.

    # Start with a blank image - somehow this causes memory cleanup $TK{'image-'.$NVP{'Id'}}=$TK{'canvas-'.$NVP{'Id'}}->Photo(-file => + "" ); # Create an image object for the image file of the correct format $TK{'image-'.$NVP{'Id'}}=$TK{'canvas-'.$NVP{'Id'}}->Photo($NVP{'Id +'}, -file +=> $NVP{'File'}, -format +=> $image{'extension'});
    Adding a trap for catching the closure of the popup window ...
    # Create a "catch" for closing the window $TK{'pw-'.$NVP{'Id'}}->protocol('WM_DELETE_WINDOW' => [\&CleanUpOn +Exit, $NVP{'Id'}]);
    And a subroutine to delete the images on the canvas as well as the images on exit ... using the magic delete -> delete(); thing
    sub CleanUpOnExit { # Get the id my $ID=shift(@_); # Delete images on the canvas $TK{'canvas-' . $ID}->delete("all"); # Delete the original image (delete $TK{'image-' . $ID})->delete(); # Destroy the popup window $TK{'pw-' . $ID}->destroy(); # Exit the Tk window Tk::exit; }
    It no longer chews up memory and even returns memory when the images are closed.

    So I wanted to say thanks.

    nzsvz9 - formerly known as the mad memory monger of my own creation

Re^4: Losing my memory
by nzsvz9 (Sexton) on Feb 06, 2021 at 13:43 UTC
    Thanks for the tips. This is what happens when you post after your daily sleep deprivation time ...