The function GetMassListFromScanNum is part of a DLL (MSFileReader) to read scientific data from a file that uses a proprietary format.

The memory leak occurs even if I never declare the array @TempScan. Calling the GetMassListFromScanNum is sufficient to allocate the memory. The documentation for pvarMassList is given here:

The mass list contents are returned in a SafeArray attached to the pvarMassList VARIANT variable. When passed in, the pvarMassList variable must exist and be initialized to VARIANT type VT_EMPTY. If the function returns successfully, pvarMassList is set to type VT_ARRAY | VT_R8. The format of the mass list returned is an array of double precision values in mass intensity pairs in ascending mass order (for example, mass 1, intensity 1, mass 2, intensity 2, mass 3, intensity 3, and so on).

Unfortunately, ->DESTROY is not a valid method for the MSFileReader software.

undef $pvarMassList does not clear the memory leak. It will prevent the script from accessing the SafeArray with the data. The memory leak is on the order of 400 kb where the compressed data file is about 300 kb. Only the SafeArray referred to by $pvarMassList is large enough to explain the memory leak. If appears that simply calling the GetMassListScanNum brings the data into memory.

Even the $thermo_raw_file->Close(); command does not deallocate the memory associated with perl in the Task manager.

I think I need a way to deallocate the SafeArray using perl (prefered) or a way to deallocate all memory associated with the MSFileReader.

I am not sure how a foreach loop helps since the memroy leak when I call the GetMassListFromScanNum function outside the loop, the loop just makes the memory leak blow up.

Thanks for the help, any further thoughts are appreciated.

In reply to Re^2: Memory Leak using Win32::OLE::Variant for a SafeArray passed by Reference by jwn
in thread Memory Leak using Win32::OLE::Variant for a SafeArray passed by Reference by jwn

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.