cygwin != Windows.

# Returns
#  (vsize, rss, shared pages, code pages, data+stack pages)
# in kilobytes.  Precision is to nearest 4k page.
# TODO: Proc::ProcessTable so that we can support non-Linux?
my $page_size_in_kb = 4;
sub _get_mem_data
{
    my ($class, $pid) = @_;

    sysopen(my $fh, "/proc/$pid/statm", 0) or die $!;
    sysread($fh, my $line, 255) or die $!;
[download]

Test suite is doesn't actually test the module, and neither module nor Makefile.PL exclude win32, so it gets a pass grade

t/00-load.t ....... ok
t/manifest.t ...... skipped: Author tests not required for installatio
+n
t/pod-coverage.t .. skipped: Test::Pod::Coverage 1.08 required for tes
+ting POD coverage
t/pod.t ........... skipped: Test::Pod 1.22 required for testing POD
[download]

I learnt a long time ago to ignore those test reports, when a module in the Win32::* namespace was condemned with an undeserved screen full of red FAILS, because it didn't install on non-Win platforms. They are next to useless IMO.

I've always preferred the simple expedient of reading the code. I learn much more that way.

---

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.

sysopen(my $fh, "/proc/$pid/statm", 0) or die $!;
[download]