A shot in the dark... maybe those Win32::Perms objects are not being reaped and/or they are causing memory leaks. Devel::Leak may help you spot what's going on. Otherwise you might want to see if you can get away with creating one Win32::Perms object and then keep feeding it new filenames.

I also suspect you really want to say scalar localtime. Right now, all you are doing is collecting the seconds component of the epoch time of the file.

Also, test your open and die if it doesn't succeed.

Minor quibble: emit the filename as the last field. If you have to eyeball the file (even though I'm assuming it's being processed downstream by another prog) it will be easier on the eyes.

--
g r i n d e r

In reply to Re: Virtual memory issue with File::Find? by grinder
in thread Virtual memory issue with File::Find? by OzzyOsbourne

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.