From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) by sourceware.org (Postfix) with ESMTPS id CEA913858C27 for ; Mon, 22 Feb 2021 20:13:10 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org CEA913858C27 Received: by mail-qk1-x72d.google.com with SMTP id 204so9015672qke.11 for ; Mon, 22 Feb 2021 12:13:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=hUHBRk49W/Wmz59SXZdUR01ODcVcTf/rIj7wHTS3AZo=; b=Cy06916dwEM3CydTQhvSy4VRI8fkjy+OsCWzuUcCGuNcRIDkr01Bg4zePwMtnBX6sK pKsH7DfrapHc3fM8VesRYROmV++V+7rDkgHOPGj+aKdxBlysHowE6wTx1qeTscd6qLkF AExj8HyeiF1DGU0xOHqbw+ArUqPICARBAOgyxqHIO6NxcYRRqpjyAv6yAjmIEQj/Exot q42qALapQiMyagJWteP6ac+W5LjUggOnCGfPKuOuvDQxiLJwc0qg67psEgegGKzo9pC3 iwTKfyIo/bOVC4pSejX6SPm6w60XGcjwh2Jr8TxZ1rEW0Kn14qNpCN6HMiLb8ok8nch4 0Qzg== X-Gm-Message-State: AOAM5319F4rcWp3nqAbmreIXSaS8Qd47RF0xAfO5GjRS77e32E+ClXzZ yDPbT0L4PyGV5/+jUFZjFoXzZhTnATmiSbT5zCuw/37DM3Y= X-Google-Smtp-Source: ABdhPJzPvJfGUfEEFiSoOfMX5atm+I6gZ3rsuRaG6GP9KCmjnRALU/mm/j6rnJp+iqTWJidthIobIXlDNfUGvdeAFqY= X-Received: by 2002:a37:b09:: with SMTP id 9mr22185179qkl.214.1614024790189; Mon, 22 Feb 2021 12:13:10 -0800 (PST) MIME-Version: 1.0 References: <003401d70864$cd3b3400$67b19c00$@gmail.com> In-Reply-To: <003401d70864$cd3b3400$67b19c00$@gmail.com> From: Doug Henderson Date: Mon, 22 Feb 2021 13:12:59 -0700 Message-ID: Subject: Re: CRITICAL ls MEMORY LEAK To: cygwin Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-0.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, FROM_LOCAL_NOVOWEL, HK_RANDOM_ENVFROM, HK_RANDOM_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Feb 2021 20:13:12 -0000 On Sun, 21 Feb 2021 at 08:21, Satalink via Cygwin 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