public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: cygwin@cygwin.com
Subject: Re: XWin server, idle, using lots of CPU time
Date: Thu, 10 Nov 2016 22:11:00 -0000	[thread overview]
Message-ID: <CAK-n8j4RUF8ks+T64=qEXEqgTA+5RAOagbBXONMQO7Ww9k7m2w@mail.gmail.com> (raw)
In-Reply-To: <a5fb9b4f-223e-bc12-9dc5-0d2f851c287a@dronecode.org.uk>

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

On Thu, Nov 10, 2016 at 9:14 AM, Jon Turney wrote:

> Possibly the problem is caused by the internal WM or clipboard threads, so
> you might try with -noclipboard or in windowed mode, and see if you see the
> same load.
>
> If that's the case, maybe running with -logverbose 3 would generate a log
> which gives more information about what unnecessary work is being done.

Thanks, Jon.

-noclipboard did not make a difference.

Running xinit instead of startxwin consumes 0% CPU time.  The X
desktop has a single xterm which I could play with.

I attached the log output from startxwin with -logverbose 3.  I opened
and closed one xterm before existing xdg.  Clipboard is disabled.

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

[-- Attachment #2: XWin.0.log --]
[-- Type: application/octet-stream, Size: 37521 bytes --]

[-- Attachment #3: Type: text/plain, Size: 218 bytes --]

--
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

  reply	other threads:[~2016-11-10 21:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10  2:06 Jim Reisert AD1C
2016-11-10 19:58 ` Jon Turney
2016-11-10 22:11   ` Jim Reisert AD1C [this message]
2016-11-10 21:42 ` Brian Inglis
2016-11-10 22:16   ` Jim Reisert AD1C
2016-11-11  6:21     ` Jim Reisert AD1C

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='CAK-n8j4RUF8ks+T64=qEXEqgTA+5RAOagbBXONMQO7Ww9k7m2w@mail.gmail.com' \
    --to=jjreisert@alum.mit.edu \
    --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).