Re^4: Hunting for a memory leak

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

Comment on Re^4: Hunting for a memory leak

Replies are listed 'Best First'.
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]

Replies are listed 'Best First'.

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]