From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: XWin.exe causes a 25% CPU load on Windows 7
Date: Thu, 16 Mar 2017 21:12:00 -0000 [thread overview]
Message-ID: <2b61e48a-065c-83bd-0b59-ebe9bac27c67@gmail.com> (raw)
In-Reply-To: <858F859BB4F2824EBAB5D4ED58214CB7016A45F4C7@NLBAWEXMBX3.infor.com>
On 3/16/2017 11:28 AM, Kees Dekker wrote:
>
> I know, the above information is vague, but do anyone have a suggestion/suggestion how to find a root cause?
> Unfortunately, I don't know when this higher-than-expected CPU load occurred for the first time. The problem became somewhat more urgent as our IT department moved our systems to a newer virus scanner, that also seems to take (much) more resources. The combination of these two makes working with this PC bad.
>
Yes
>
> --
> Problem reports: http://cygwin.com/problems.html
See the above.
--
cyg Simple
--
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
next prev parent reply other threads:[~2017-03-16 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 15:28 Kees Dekker
2017-03-16 21:12 ` cyg Simple [this message]
2017-03-20 7:37 ` Kees Dekker
2017-03-22 20:05 ` Jon Turney
2017-04-24 16:52 ` Kees Dekker
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=2b61e48a-065c-83bd-0b59-ebe9bac27c67@gmail.com \
--to=cygsimple@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).