Re^2: Hunting for a memory leak

Replies are listed 'Best First'.
Re^3: Hunting for a memory leak by BrowserUk (Patriarch) on Aug 07, 2012 at 17:30 UTC
contrary to your diagnosis, the documentation says that use of the -file option does not cause this behaviour. Hm. Here are my findings using the -file option: `[18:25:56.31] C:\test>dir test.png 26/05/2012 11:30 7,133 test.png [18:26:17.25] C:\test>986015.pl start perl.exe 6476 Console 1 29 +,328 K end start perl.exe 6476 Console 1 34 +,652 K end start perl.exe 6476 Console 1 38 +,348 K end start perl.exe 6476 Console 1 38 +,180 K end start perl.exe 6476 Console 1 39 +,324 K end start perl.exe 6476 Console 1 42 +,816 K end start perl.exe 6476 Console 1 45 +,948 K end` [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". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply] [d/l]
Re^4: Hunting for a memory leak by perldough (Sexton) on Aug 08, 2012 at 14:10 UTC
I didn't mean to challenge your finding; rather, I meant to imply that I could maybe look for a way of coaxing my code into exhibiting the behaviour posted in the bug report in order to eliminate the leak. I any case, thanks for taking the time for confirming this. Perldough	[reply]
Re^5: Hunting for a memory leak by BrowserUk (Patriarch) on Aug 08, 2012 at 14:20 UTC
It is quite possible that I am using a down-level tk/tk::photo relative to the guy who reported the bug. I only posted my findings to warn you that you should check your installation before assuming the fix. 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". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply]
Re^3: Hunting for a memory leak by BrowserUk (Patriarch) on Aug 07, 2012 at 18:30 UTC
Looking in the POD for Tk::Image it says: CAVEATS It's necessary to use the "delete" method to delete an image object and free memory associated with it. Just using a lexical variable for storing the image object and letting the variable to go out of scope or setting to undef is not sufficient. That said, I tried adding `$ZC->centerTags($dwg); $img->delete; undef $img;` [download] And it made no difference. 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". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply] [d/l]
Re^3: Hunting for a memory leak by Anonymous Monk on Aug 08, 2012 at 03:13 UTC
Thank you for this. I believe I need to start doubting the CPAN modules a little more. Tk modules are notorious for leaks -- also , if the module builds any kind of tree, and grepping the source for "weak" returns no hits, 97/100 its leaking :)	[reply]
Re^4: Hunting for a memory leak by perldough (Sexton) on Aug 08, 2012 at 14:19 UTC
That's interesting. Would you mind explaining why that is? Perldough	[reply]
Re^5: Hunting for a memory leak by Anonymous Monk on Aug 10, 2012 at 07:44 UTC
That's interesting. Would you mind explaining why that is? Because that is just the way it is :) Trees means circular references (memory leak unless you take some steps), and Tk encourages both circular references and closures -- just look in the bug cue for any Tk- distribution, you'll see lot of reports of leaks	[reply]