[Xastir] Fwd: [Bug 454740] [NEW] xastir consumes CPU time in X11 socket I/O

[David Aitcheson]

Kevin,

I believe this activity level is normal.  I am forwarding this to the
Xastir discussion list.  Please consider joining the list as that is
where the true developers of Xastir hang out.

The main Xastir page is now at http://www.xastir.org/wiki/index.php/Main_Page

73
Dave
KB3EFS


---------- Forwarded message ----------
From: Kevin Otte <nivex at nivex.net>
Date: Sun, Oct 18, 2009 at 11:44 AM
Subject: [Bug 454740] [NEW] xastir consumes CPU time in X11 socket I/O
To: david.aitcheson at gmail.com


Public bug reported:

Binary package hint: xastir

kjotte at zarya:~$ lsb_release -rd
Description:    Ubuntu 9.04
Release:        9.04

kjotte at zarya:~$ apt-cache policy xastir
xastir:
 Installed: 1.9.4-3
 Candidate: 1.9.4-3
 Version table:
 *** 1.9.4-3 0
       500 http://archive.linux.duke.edu jaunty/universe Packages
       100 /var/lib/dpkg/status

After upgrading from Intrepid (xastir 1.9.2) to Jaunty I noticed my CPU
was running at a constant ~10%.  Running an strace revealed there was
quite a bit time spent timing out of polls on the X11 socket fd.  I
tried setting the DISPLAY to use TCP instead of UNIX sockets, but the
high poll activity still occurred.

** Affects: xastir (Ubuntu)
    Importance: Undecided
        Status: New

--
xastir consumes CPU time in X11 socket I/O
https://bugs.launchpad.net/bugs/454740
You received this bug notification because you are subscribed to xastir
in ubuntu.

Status in “xastir” package in Ubuntu: New

Bug description:
Binary package hint: xastir

kjotte at zarya:~$ lsb_release -rd
Description:    Ubuntu 9.04
Release:        9.04

kjotte at zarya:~$ apt-cache policy xastir
xastir:
 Installed: 1.9.4-3
 Candidate: 1.9.4-3
 Version table:
 *** 1.9.4-3 0
       500 http://archive.linux.duke.edu jaunty/universe Packages
       100 /var/lib/dpkg/status

After upgrading from Intrepid (xastir 1.9.2) to Jaunty I noticed my
CPU was running at a constant ~10%.  Running an strace revealed there
was quite a bit time spent timing out of polls on the X11 socket fd.
I tried setting the DISPLAY to use TCP instead of UNIX sockets, but
the high poll activity still occurred.