desktop-packages team mailing list archive

[Evan Peck <151536@xxxxxxxxxxxxxxxxxx>]

** Changed in: evolution-data-server (Ubuntu)
       Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/151536

Title:
  [MASTER] E-D-S hangs on login and uses 100% cpu

Status in Evolution Data Server:
  Expired
Status in “evolution-data-server” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: evolution-data-server

  <PLEASE> -- do not add simple "me too" comments, they do not help: we
  already *know* this is a problem, and these comments only make it more
  difficult to find potentially important data in the bug. If you have
  the knowledge and time to help debug, your help *is* appreciated. Go
  to #ubuntu-bugs in irc.freenode.net, and discuss it there. I am sure
  that any one of us will be more than happy to get on with this
  ;-)</PLEASE>

  On login evolution-data-server uses 100% cpu. At login evolution-
  alarm-notify is auto-started by gnome-session; e-a-n kicks in E-D-S
  and, for yet an unknown reason, E-D-S enters a loop. strace on E-D-S
  shows a sequence of very fast poll() calls; a strace on e-a-n shows
  e-a-n waiting for an event. This seems to happen on some machines, but
  not all. It affects both Evolution users and non-users -- E-D-S is
  still installed under Gnome even if you do not use the Evolution mail
  client.

  All symptoms are of a race condition, very early in E-D-S or a library
  startup. Backtraces are inconclusive, and show slightly different code
  paths. I cannot reproduce it on my machine (an AMD64 dual-core), no
  matter what I try.

  I would like to know what Linux and hardware architecture, and how
  many CPUs for those that are *frequently* hit (for example, {linux64,
  AMD64, 2 CPUs}, meaning I am running linux64 on an AMD64 with two
  CPUs; {linux32, AMD64, 4 CPUs}, meaning I am running linux32 Intel on
  an AMD64 with  4 CPUs).

  Right now we are considering this as a race very early on session
  startup, perhaps caused by the current placement of e-a-n on the
  default session list (with the default priority of 50). I myself still
  cannot reproduce it, and I wonder if having a dual-CPU machine, and/or
  linux64, and/or AMD64, makes the race more difficult to happen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/151536/+subscriptions