[Bug 148454] Re: console-kit-daemon spawns too many threads

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=457845.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2008-08-04T22:25:46+00:00 Adam wrote:

Description of problem:
I have upgraded a new F9 system to Rawhide.  Whereas other recent bugs related to switching runlevels, I have seen the creation of lots of console-kit-daemon processes when going straight into runlevel 5.  As of this writing, there are 62 such processes on the system, which has been up 30 minutes.

Version-Release number of selected component (if applicable):
ConsoleKit-0.3.0-1.fc10.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

excerpt of pstree output:

init─┬─/usr/bin/sealer
     ├─NetworkManager───{NetworkManager}
     ├─acpid
     ├─anacron
     ├─atd
     ├─auditd─┬─audispd───{audispd}
     │        └─{auditd}
     ├─avahi-daemon───avahi-daemon
     ├─bonobo-activati───{bonobo-activati}
     ├─clock-applet
     ├─console-kit-dae───62*[{console-kit-dae}]
     ├─crond
     ├─cupsd
     ├─2*[dbus-daemon───{dbus-daemon}]
     ├─2*[dbus-launch]

Reply at:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/148454/comments/50

------------------------------------------------------------------------
On 2008-08-05T22:28:43+00:00 Matthias wrote:

This is not a bug, it is working around the limitiations of the linux vt system.
These are threads, one for each vt, sleeping in VT_WAITACTIVE.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/148454/comments/51

------------------------------------------------------------------------
On 2009-03-24T20:57:13+00:00 Jason wrote:

Created attachment 336537
Patch for ConsoleKit 0.30 to remove so many threads

This patch changes ConsoleKit to use an new VT ioctl and wait on a
terminal switch without requiring a thread for every possible VT.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/148454/comments/80

------------------------------------------------------------------------
On 2009-03-24T20:59:26+00:00 Jason wrote:

Created attachment 336538
Kernel patch to add new VT ioctl.

This patch must be added to the kernel to support the previous patch for
ConsoleKit.  Basically we add a VT_WAITSWITCH ioctl which sleeps until
any virtual console switch occurs; this allows ConsoleKit to only use
one thread to wait, and it uses the VT_GETSTATE ioctl to determine the
active VT (as with Solaris implementation).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/148454/comments/81

------------------------------------------------------------------------
On 2009-10-29T00:20:30+00:00 Topher wrote:

FYI: I'm seeing the same thing in F12. (63 console-kit-daemon processes)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/148454/comments/97


** Changed in: consolekit (Fedora)
   Importance: Unknown => Medium

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

Title:
  console-kit-daemon spawns too many threads

Status in ConsoleKit:
  Confirmed
Status in consolekit package in Ubuntu:
  Opinion
Status in consolekit package in Fedora:
  Invalid

Bug description:
  since upgrading to gutsy beta htop shows about fifty processes like
  the following

  pid user pri ni virt res shr s cpu% mem% time+ command
  7582 root 23 0 7456 2016 1336 s 0.0 0.2 0:00.00 /usr/sbin/console-kit-deamon

  It maybe the case that console-kit-daemon starts a thread for each
  console that can theoretically exist. On Linux
  (/usr/include/linux/vt.h) MAX_NR_CONSOLE is defined to be 63.

  Note that those processes do not show up in DEFAULT top or ps output
  --BUT-- if you run either of those tools with the -H parameter, so as
  to display all the threads of a process, then they do show up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/consolekit/+bug/148454/+subscriptions