Re^3: Hunting for a memory leak

[BrowserUk]

in reply to Re^2: Hunting for a memory leak
in thread Hunting for a memory leak

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

[perldough]

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

[BrowserUk]

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.