I've done very little with Win32::OLE and it was several years ago, but I do recall that it leaked quite substantially when called repetitively. From memory, the leaks were deep inside the OLE code and beyond the control of the user programs. Each new OLE object created never quite seemed to clean up all it's memory when it was undef'd.

My suggestion to you would be to split your code into two parts. Leave the directory monitoring code in the service and move the OLE code into a separate script. When the service detects a file for processing, it invokes the other script with the name/path of the file as an argument. When the other script terminates, it will clean up it's own memory and bypass the problem.

This also open the possibility of using system] 1, qq[yourOleScript.pl $theFile2BProcessed]; which will 'detach' (run asynchronously), the OLE script and allow your service to respond more quickly to the next file by running multiple file concurrently.

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.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re: memory (leaks and management) by BrowserUk
in thread memory (leaks and management) by soliplaya

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.