Are the boxes under quite a lot of load? Does this load vary during the day and does the occurence of the problem relate to this in any way?

You mention that the scripts are spawning children. Are they waiting for them to exit or running in parallel with them? How about the child scripts? Does task manager show a shedload of child processes running?

If you can't capture the problem at the time, turn on performance monitoring and graph these things over the day, so you can look for spikes/ceilings around the time of the problem. Also, don't just look at the bad machines, duplicate all the measurements on the 'good' ones and look for differences.

Do the machines tend to get sick at approx the same time (suggests an external, i.e. network factor)? Look at the network topology, do the sick machines share any factors there (same switch?)?

Some possibilities: 'memory' (vm exhaustion?), number of handles per process, maximum process stack depth (not perl stack, the underlying C stack), number of threads per proc, total number of procs running on the box, total number of threads on the box, etc.

Since its intermittent, it could be a more classic race, caused by general slowdown etc. So, lastly, can you 'induce' an episode by adding some load to one of your machines? Try different types of load (a cpu burner, a mem hog, a ping flood, a process which starts a lot of children).

It sounds like a build environment, so I wouldn't imagine the perl is too complex - is this right? Or is there a lot of hairy code in there? And again, what about the child processes?

Hope this helps, intermittent probs are always tough.

Good luck.


In reply to Re: Win32 - Memory can not be "read" by jbert
in thread Win32 - Memory can not be "read" by HuckinFappy

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.