public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Kees Dekker <Kees.Dekker@infor.com>
To: cygwin-xfree <cygwin-xfree@cygwin.com>
Subject: RE: Xwin.exe always take about 50% CPU load on Windows 7 with XDCMP connection
Date: Mon, 05 Mar 2012 07:39:00 -0000 [thread overview]
Message-ID: <45282936A11F374E9592C1F4C7AB9AFE32E69F3E2D@NLBAWEXMB4.infor.com> (raw)
In-Reply-To: <4F5115C3.50100@dronecode.org.uk>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1752 bytes --]
Hi,
Thanks for your reply. I looked in the mail archives about what was solved, and thus missed indeed this announcement. So I apparently looked at the wrong place, or the wrong month of the archive, sorry.
My keyword where I searched for was 'CPU' 'load'.
Kees
On 02/03/2012 09:24, Kees Dekker wrote:
> Iâm using Xwin.exe (version 5. Feb 2012, X.org servers â 1.11.4-3) on my
> Windows 7 system. When connecting with XDCMP (using startxdcmp.bat, with
> %RUN% XWin -query %REMOTE_HOST% -once -lesspointer -clipboard
> -emulate3buttons), after connect, the CPU load is about 50%. Even when
> nothing is done (only the CDE desktop is running, nothing else).
>
> On another Windows 7 system, also connecting with XDCMP to the same server,
> same CDE, the CPU load is not that high. The version of XWin is one of 5.
> Feb 2009.
>
> The XCDMP server is a Solaris 10 system, using Solaris classic CDE (not the
> Java Desktop environment). The high CPU load did not happen when the CDE
> waits for the logon screen, but happens as soon as login was completed.
>
> BTW. Just when I was writing this email I decided to check (again) for a
> newer version, and there was one⦠Moving to X.org servers 1.11.4-5 seems to
> solve this issue âº. However, I did not find any release note telling that
> this problem was solvedâ¦.
I'm not sure where you were looking if you didn't find [1].
'On Cygwin 1.7.10 this caused XWin to spin, when started from a non-cygwin
process, spamming the log with "_XSERVTransSocketUNIXAccept: accept() failed"
messages.'
[1] http://cygwin.com/ml/cygwin-xfree-announce/2012-02/msg00004.html
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
\x16º&s(0|_ç«zÛ«};ãb²Ö«r\x172\b§ÅúÞ
prev parent reply other threads:[~2012-03-05 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 9:25 Kees Dekker
[not found] ` <4F5115C3.50100@dronecode.org.uk>
2012-03-05 7:39 ` Kees Dekker [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=45282936A11F374E9592C1F4C7AB9AFE32E69F3E2D@NLBAWEXMB4.infor.com \
--to=kees.dekker@infor.com \
--cc=cygwin-xfree@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).