From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: CRITICAL ls MEMORY LEAK
Date: Mon, 22 Feb 2021 13:12:59 -0700 [thread overview]
Message-ID: <CAJ1FpuMbx1pyOqoRSwgieQbGPgcXOOiUusFtsmqKWoyJdzF0pg@mail.gmail.com> (raw)
In-Reply-To: <003401d70864$cd3b3400$67b19c00$@gmail.com>
On Sun, 21 Feb 2021 at 08:21, Satalink via Cygwin <cygwin@cygwin.com> wrote:
>
> I deal with a lot of very large files on a regular basis. I've noticed that
> when I delve into these directories using in mintty and issue the command ls
> -l (or ls -color=auto), a very large junk of memory is consumed. The
> memory leak seems to be proportionate to the number and size of files within
> the containing folder.
This is likely due to your virus scanner. If those files contain
non-executable content, it is probably safe to disable virus scans for
those files.
Something that ls does is triggering the scan. That scan causes the
virus scanner to read the entire file. You should see extraordinary
GPU and disk activity for some time after the ls completes. There
might be processes or at least threads for each file being scanned.
Hopefully you will be able to identify a common folder in the path to
those files where it is safe to disable scanning for that folder and
all folders and files within that folder.
HTH
Doug
--
Doug Henderson, Calgary, Alberta, Canada - from gmail.com
next prev parent reply other threads:[~2021-02-22 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 15:18 neal.garrett
2021-02-21 18:05 ` Brian Inglis
2021-02-22 20:12 ` Doug Henderson [this message]
2021-02-22 20:30 ` Brian Inglis
2021-02-22 21:50 ` Hans-Bernhard Bröker
2021-02-22 23:47 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ1FpuMbx1pyOqoRSwgieQbGPgcXOOiUusFtsmqKWoyJdzF0pg@mail.gmail.com \
--to=djndnbvg@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).