[Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()

[James Hunt]

Right. So to be completely clear, by calling nih_dbus_setup(), nih was
registering a libdbus handler that runs on the client side such that
whenever libdbus deemed necessary, it would attempt to wake up the
clients main loop by calling nih_main_loop_interrupt(). However, since
the client didn't have an nih main loop, the interrupt pipe was never
drained and eventually filled leading to the EAGAIN tight loop.

Yes, I agree - maybe it should have been called
nih_dbus_main_loop_setup() to make its usage clearer.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libnih in Ubuntu.
https://bugs.launchpad.net/bugs/1303649

Title:
  systemd-logind spins in cgmanager_ping_sync()

Status in “cgmanager” package in Ubuntu:
  Confirmed
Status in “libnih” package in Ubuntu:
  Confirmed
Status in “lxc” package in Ubuntu:
  Confirmed
Status in “systemd” package in Ubuntu:
  Confirmed

Bug description:
  systemd-logind is consuming a high level of cpu on a continual basis:

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                                                
    676 root      20   0   43644   2144   1568 R 100.0  0.0  74:43.77 systemd-logind

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd-services 204-5ubuntu17
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 09:09:37 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-23 (348 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions