xastir consumes CPU time in X11 socket I/O

[Kevin Otte]

Binary package hint: xastir

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

kjotte@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.

[Kamal Mostafa (kamalmostafa)]

The problem still occurs in the latest upstream version xastir-1.9.6 ( available for testing in my PPA: https://launchpad.net/~kamalmostafa/+archive/xastir ).

Strace on xastir-1.9.6 shows this sequence spinning hard:

sched_yield() = 0
sched_yield() = 0
read(5, 0x1694914, 4096) = -1 EAGAIN (Resource temporarily unavailable)
read(5, 0x1694914, 4096) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN|POLLPRI}], 2, 9) = 0 (Timeout)
poll([{fd=6, events=POLLIN|POLLPRI}], 1, 0) = 0 (Timeout)
read(5, 0x1694914, 4096) = -1 EAGAIN (Resource temporarily unavailable)
read(5, 0x1694914, 4096) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN|POLLPRI}], 2, 0) = 0 (Timeout)
poll([{fd=6, events=POLLIN|POLLPRI}], 1, 0) = 0 (Timeout)
[...]

[Kamal Mostafa (kamalmostafa)]

Reported the bug against xastir-1.9.6 to the project home at SourceForge; added bug watch.

[Iain R. Learmonth (irl)]

Last activity on this bug was 2010. Can anyone say if this is still an issue in version 2.0.6?

[Kevin Otte (nivex)]

Going back through old bug reports and stumbled across this still open. Fired up xastir on my ham box to check it out.

Machine I'm running it on is significantly newer, but I am indeed still seeing about an 8% CPU load from the xastir 2.0.6 process on Ubuntu 15.10. I strace'd the running process and am still seeing a similar tight loop but with recvmsg() rather than read().

[David Aitcheson - KB3EFS (kb3efs)]

Kevin, Iain, Kamal, et al,

_ALL_ Xastir bugs and problems are handled on/at <email address hidden>.

ALL support is to be routed via that reflector.

The CPU load you are seeing is normal for all operating systems as far
as I know.

Many are now running Xastir on headless Raspbery-Pi's without problems.

As far as I am concerned this bug should be closed due to old age and
lack of any others complaining about the CPU load factor.

73
Dave
KB3EFS

On 11/04/2015 03:36 PM, Kevin Otte wrote:
> Going back through old bug reports and stumbled across this still open.
> Fired up xastir on my ham box to check it out.
>
> Machine I'm running it on is significantly newer, but I am indeed still
> seeing about an 8% CPU load from the xastir 2.0.6 process on Ubuntu
> 15.10. I strace'd the running process and am still seeing a similar
> tight loop but with recvmsg() rather than read().
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/454740
>>
>> Title:
>> xastir consumes CPU time in X11 socket I/O
>>
>> Status in xastir:
>> Unknown
>> Status in xastir package in Ubuntu:
>> Triaged
>>
>> Bug description:
>> Binary package hint: xastir
>>
>> kjotte@zarya:~$ lsb_release -rd
>> Description: Ubuntu 9.04
>> Release: 9.04
>>
>> kjotte@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.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/xastir/+bug/454740/+subscriptions
>>
>

[FanJun Kong - ( BH1SCW ) (fjkong)]

so could we close it now?

[Kevin Otte (nivex)]

Might as well. When upstream says "Well no one else is complaining" you're not likely to get anywhere. Just because CPUs have gotten faster doesn't mean the problem has gone away, only masked.

[David Aitcheson - KB3EFS (kb3efs)]

Gentlemen,

Please kindly direct all future bug complaints to <email address hidden>

The developers are always active on that Mailman List-serve.

Additionally this may have been fixed in a later release, the current
release is V2.0.9 built from source on GitHub and works FB for me.

You are addressing V1.9.4-3 which is known to have had issues that are
most definitely fixed in more recent versions.

My suggestion to you both is to subscribe to <email address hidden> via
http://xastir.org/mailman/listinfo/xastir and join the discussion.

Very 73,
Dave - KB3EFS

On 11/07/2016 11:05 AM, Kevin Otte wrote:
> Might as well. When upstream says "Well no one else is complaining"
> you're not likely to get anywhere. Just because CPUs have gotten
> faster doesn't mean the problem has gone away, only masked.

[Kevin Otte (nivex)]

Upstream doesn't care. Closing this out to clean up my bug list.