public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: David Arnstein <arnstein@pobox.com>
Subject: Re: X11 becomes unresponsive with complex client programs
Date: Mon, 16 Jan 2017 14:09:00 -0000	[thread overview]
Message-ID: <41a04977-999a-728b-1e0d-4dc40c634ac3@dronecode.org.uk> (raw)
In-Reply-To: <3dcb5e0d-45bd-cb01-ac46-1a9c36785108@pobox.com>

On 14/01/2017 01:38, David Arnstein wrote:
> My cygwin installation can display simple X11 clients such as xterm. A
> complex client such as git-cola, launched from a remote RedHat Linux
> machine, will cause all X11 windows under cygwin to become unresponsive.
> Windows Task Manager says "not responding."
>
> This problem occurs with recent releases of Cygwin/X11. The attached
> cygcheck.out indicates the last X11 version that works well: 1.18-4.1.
> All other cygwin packages are up to date.

Thanks for reporting this problem.

Unfortunately, I couldn't reproduce it.

However, I suspect this may be caused by switching to the smart 
scheduler by default in xorg-server 1.19.0-1.

So, the first thing I'd suggest you try is adding -dumbSched to the X 
server options to see if this makes a difference (e.g. 'startxwin -- 
-dumbSched'

-- 
Jon Turney
Volunteer Cygwin/X X Server maintainer

--
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:[~2017-01-16 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-14  1:38 David Arnstein
2017-01-16 14:09 ` Jon Turney [this message]
2017-01-16 17:49   ` David Arnstein

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=41a04977-999a-728b-1e0d-4dc40c634ac3@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=arnstein@pobox.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).