in reply to Re^3: Memory leak
in thread Memory leak

Thank you, that would certainly explain it as a couple of the top-level windows get dragged to full-screen. And I've been destroy-ing those regularly. Sometimes I automate the whole sequence for many a file so that destroy might happen a hundred times. A couple of times I thought I'd crashed the OS...with 4GB...but now that I recall it seems as if only X-windows had locked. So it's the GUI not the OS which crashed, I guess.

This withdraw and re-configure business does sound quite a pain to deal with...ex-post-facto...as now I must do. But I'll start chipping away at it.

Thank you again,

Gan

Replies are listed 'Best First'.
Re^5: Memory leak
by zentara (Cardinal) on Jan 15, 2005 at 13:10 UTC
    I learned the hard way too( which is why I havn't forgot :-) ). But the rewrite went pretty easy, since most of the logic was already thought out, and it was just changing the way things get displayed. Also, your next project will be alot easier, since you will know this from the beginning, and design accordingly.

    You think "what boxes" am I going to be displaying to the screen"? Then put them into hashes to make them easy to loop thru, like:

    my %toplevel_1; my %toplevel_2; .... ... $toplevel_1{'label'} = $tl_1->Label(..etc); $toplevel_1{'text'} = $tl_1->Text(..etc); $toplevel_1{'label'}->configure(-text => $new_text); $toplevel_1{'text'}->delete('1.0','end');

    I'm not really a human, but I play one on earth. flash japh