From: Jan-Marek Glogowski <glogow@fbihome.de>
To: cygwin@cygwin.com
Subject: Re: CPU hogging by dysfunctional bash or zsh when started via mintty Cygwin terminal link
Date: Fri, 14 Feb 2020 11:47:00 -0000 [thread overview]
Message-ID: <5347a7b6-0a2e-7e1a-ca41-d9acda7f5d23@fbihome.de> (raw)
In-Reply-To: <fee71494-4173-305f-8950-d4cac7754c13@cornell.edu>
Am 14.02.20 um 03:39 schrieb Ken Brown:
>
> Your strace output shows that sysfer.dll is loaded. This is apparently
> a component of Symantec Endpoint Protection. Could the latter be
> interfering with Cygwin? See
>
> Â https://cygwin.com/faq/faq.html#faq.using.bloda
Just booted the Windows VM to quick-check changing AV settings and the
problem is gone. Without any changes.
Jan-Marek
(who is now reminded of the old fix: "have you tried to turn it off and
on again"...)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2020-02-14 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 2:09 Jan-Marek Glogowski
2020-02-14 2:40 ` Ken Brown
2020-02-14 11:47 ` Jan-Marek Glogowski [this message]
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=5347a7b6-0a2e-7e1a-ca41-d9acda7f5d23@fbihome.de \
--to=glogow@fbihome.de \
--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).