in reply to Re^3: Perl system command memory usage in threads
in thread Perl system command memory usage in threads

Yes, that is the exact code run on the test system. I've also included another update indicating system information and perl -v output.

For what its worth, the systems I'm testing this on are virtual machines, and are experiencing some issues. I just did not think these issues could/would cause a problem like this?

Running the code on my workstation, on active perl 5.20.2, i too see no memory leak and similar numbers.

  • Comment on Re^4: Perl system command memory usage in threads

Replies are listed 'Best First'.
Re^5: Perl system command memory usage in threads
by BrowserUk (Patriarch) on Jul 31, 2015 at 22:31 UTC
    For what its worth, the systems I'm testing this on are virtual machines,

    That is almost certainly the cause; and I seriously doubt that there is anything that can be done either in your script or perl to alleviate it.

    About the only thing that might offer a solution (besides dropping out of the VM) would be to try a different VM.

    When I played with VMs a couple of years ago I had less problems with MS Virtual PC than Oracle's Virtual Box; but both gave me problems -- mostly with networking for the stuff I was doing. However, both have seen significant updates since, so my information is out of date.

    FWIW: one of my customers uses VMWare and they are very happy with it; but they can afford to employ expertise and pay for support contracts.

    Anyone got any experience of this phone's predecessor?

    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    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". I knew I was on the right track :)
    In the absence of evidence, opinion is indistinguishable from prejudice.
    I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!
[reply]

      Well, upgrading the vm to perl 5.20.2 seems to have actually fixed the problem. So it looks like the bug was in perl 5.18, maybe specifically perl 5.18 on a VM or Server 2008? Dunno, very weird. At least it's an easy work around.

      Also, this seemed to have solved my second question as well...no more hanging from the un-synchronized system commands. Go figure

      Thank you for taking the time to help! Much appreciated

[reply]
        upgrading the vm to perl 5.20.2 seems to have actually fixed the problem. ... Also, this seemed to have solved my second question

        Cool. Glad you have a solution. Looks like I need to complete my transition to 5.20.

        Anyone got any experience of this phone's predecessor?

        With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
        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". I knew I was on the right track :)
        In the absence of evidence, opinion is indistinguishable from prejudice.
        I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!
[reply]

In Section Seekers of Perl Wisdom