in reply to Re: File::Find hogging memmory.
in thread File::Find hogging memmory.

First of all, did you follow gellyfish's suggestion and compare the versions of the File::Find module itself? Did they report version differences?

Secondly, while you included code to show how it is deciding to do something with the desired files, you showed nothing regarding what you are doing with the match. Are you storing something related to the match in an array, hash, object, or other "growable" data structure of some kind?

My only other concern would be in that you are creating what is essentially a daemon process that runs continuously, with short (3s) pauses between processing. Not knowing your particular application, I cannot say this is or is not the best way to approach it, but if it is not essential to the application, you might consider limiting the number of times the app runs, in combination with the system's cron (or similar) feature, to keep the app from running too long if it does indeed have some form of memory leak.

Not sure that helps, but hope it at least gives you something to look at.

Replies are listed 'Best First'.
Re^3: File::Find hogging memmory.
by asifk1981 (Novice) on Oct 14, 2004 at 05:43 UTC
    The two Find.pm versions are compared and they are found to be the same (1.4). Still when I do a manual diff between them I could see the differences, as mentionjed in the previous mail from me. Please not thet this Find opetations are not part of any application or any other processes. I have written some test scripts that have only one Find operation in it, and obserbved that one of the servers hoggs a lot of tmemmory for the process. Please share ur ideas...