/usr/lib/evolution/evolution-calendar-factory consume 99% cpu

Can you please provide details as to what you were doing when this happened and how to reproduce it?

I'm having the same problem on my Ubuntu Desktop. The problem appears periodically but I'm not sure what triggers it.

my english is poor,Can I peak chinese!

I'am sorry,I can't reproduce this bug.I’ll take care of this bug next times
and record condition about bug appear。

On Mon, Oct 29, 2012 at 6:41 PM, Matt Fischer <email address hidden>wrote:

> Can you please provide details as to what you were doing when this
> happened and how to reproduce it?
>
> ** Changed in: ubuntu-nexus7
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1072406
>
> Title:
> /usr/lib/evolution/evolution-calendar-factory consume 99% cpu
>
> Status in Ubuntu on the Nexus 7:
> Incomplete
>
> Bug description:
> evolution-calendar-factory of process consume 99% cpu ,I can't find
> why, current
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-nexus7/+bug/1072406/+subscriptions
>

This issue happened to me also, in LXDE. I also don't know what caused it, because I just happened to view the open processes and saw it after having the device on for a while.

This is happening to me right now.
I'm not on a nexus. I'm on a Lenovo X220.
Using 12.10

Same here on a 64bit ubuntu 12.10 (upgraded from beta), in gnome-shell.
htop shows that this process is spawned by the lightdm user (???)

Possible dupe of https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/151536

Status changed to 'Confirmed' because the bug affects multiple users.

I find the way reproduct it. when I log out and log in ubuntu on nexus 7
Because I can't touch screen,process of evolution-calendar-factory auto
run and consume more than 80% cpu.

On Mon, Nov 5, 2012 at 11:43 PM, Matt Fischer <email address hidden>wrote:

> ** Project changed: evolution-data-server => evolution-data-server
> (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1072406
>
> Title:
> /usr/lib/evolution/evolution-calendar-factory consume 99% cpu
>
> Status in Ubuntu on the Nexus 7:
> Confirmed
> Status in “evolution-data-server” package in Ubuntu:
> New
>
> Bug description:
> evolution-calendar-factory of process consume 99% cpu ,I can't find
> why, current
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-nexus7/+bug/1072406/+subscriptions
>

Status changed to 'Confirmed' because the bug affects multiple users.

I, too, am having to deal with evolution-calendar-factory taking up between 96% and 100% CPU, apparently started by the lightdm user. I've also had several evolution-related crashes, but after the first 5 times, i just set it to ignore. I am running a fresh install of 12.10 64bit on an AMD A8 laptop. I use gnome-shell and the only calendar connection I use is to my google calendar. HTH

I see the same thing. I'm using 12.10 with XFCE and this problem started at boot today. I applied plenty of patches yesterday, but I'm not sure of the cause.

Top output:

 1833 lightdm 20 0 661m 11m 7244 R 99.6 0.1 15:20.80 evolution-calen

$ ps -ef | grep evolu
lightdm 1833 1 98 10:16 ? 00:15:30 /usr/lib/evolution/evolution-calendar-factory

Workaround: ;-)

sudo killall -9 evolution-calendar-factory

Happens from time to time, I notice it by my laptop's fans starting to be audible. Indeed the process seems to be owned by lightdm, but I haven't seen anything that clearly reproduces it - possibly switching between users / logging out/in instead of single user mode or rebooting.

Are there any additional logs or debugging steps we can take to try to pin this down further?

Same here, noticed a few times that fan is very loud and happened to notice lightdm owned process evolution-calendar-factory was causing it. Killing it brings cpu usage down.

Linux jaytec 3.6.7-030607-generic #201211171710 SMP Sat Nov 17 22:10:54 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Added some ubuntu-bug generated info.

I am having this problem in 12.10 64 bit.

I am using Unity but have gnome shell installed. All evo accounts are disabled, including calendar and Evo is off line.

Added workaround:
sudo apt-get remove evolution-data-server

Warning: That will remove:
evolution-data-server gnome-contacts libfolks-eds25

I am currently affected by this bug. I just did a fresh install of 12.10 today, and this process has been pegged at 100% CPU for a few hours now.

Killing the process has no effect - it just spawns again.

Could somebody get a stacktrace (or several ones) of the process using gdb (with debug symbols installed) to give an idea of where it's being busy?

Stack trace:

#0 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x7fb2b801b010, hash_table=0x7fb2b00026a0)
    at /build/buildd/glib2.0-2.34.1/./glib/ghash.c:410
#1 g_hash_table_remove_internal (hash_table=0x7fb2b00026a0, key=0x7fb2b801b010, notify=1)
    at /build/buildd/glib2.0-2.34.1/./glib/ghash.c:1269
#2 0x00007fb2ce526a5d in cal_backend_contacts_remove_book_record (cbc=0x12da0e0, source=0x7fb2b801b010)
    at e-cal-backend-contacts.c:231
#3 0x00007fb2d5e885c4 in g_cclosure_marshal_VOID__OBJECTv (closure=0x12e4950, return_value=<optimized out>,
    instance=0x12b7dc0, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>,
    param_types=0x12b5b70) at /build/buildd/glib2.0-2.34.1/./gobject/gmarshal.c:1312
#4 0x00007fb2d5e85407 in _g_closure_invoke_va (closure=0x12e4950, return_value=0x0, instance=0x12b7dc0,
    args=0x7fffdb2e0a38, n_params=1, param_types=0x12b5b70)
    at /build/buildd/glib2.0-2.34.1/./gobject/gclosure.c:840
#5 0x00007fb2d5e9ddf6 in g_signal_emit_valist (instance=0x12b7dc0, signal_id=<optimized out>, detail=0,
    var_args=var_args@entry=0x7fffdb2e0a38) at /build/buildd/glib2.0-2.34.1/./gobject/gsignal.c:3211
#6 0x00007fb2d5e9e642 in g_signal_emit (instance=instance@entry=0x12b7dc0, signal_id=<optimized out>,
    detail=detail@entry=0) at /build/buildd/glib2.0-2.34.1/./gobject/gsignal.c:3356
#7 0x00007fb2d6363bb9 in source_registry_remove_source (source=0x7fb2b801b010, registry=0x12b7dc0)
    at e-source-registry.c:605
#8 source_registry_object_removed_idle_cb (user_data=<optimized out>) at e-source-registry.c:656
#9 0x00007fb2d5bc4ab5 in g_main_dispatch (context=0x12ac680) at /build/buildd/glib2.0-2.34.1/./glib/gmain.c:2715
#10 g_main_context_dispatch (context=context@entry=0x12ac680) at /build/buildd/glib2.0-2.34.1/./glib/gmain.c:3219
#11 0x00007fb2d5bc4de8 in g_main_context_iterate (context=0x12ac680, block=block@entry=1,
    dispatch=dispatch@entry=1, self=<optimized out>) at /build/buildd/glib2.0-2.34.1/./glib/gmain.c:3290
#12 0x00007fb2d5bc51e2 in g_main_loop_run (loop=0x12ac7e0) at /build/buildd/glib2.0-2.34.1/./glib/gmain.c:3484
#13 0x00007fb2d65b7de8 in dbus_server_run_server (server=0x12ad020) at e-dbus-server.c:222
#14 0x00007fb2d37a5bb8 in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
#15 0x00007fb2d37a55c0 in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
#16 0x00007fb2d5e8612b in g_cclosure_marshal_generic_va (closure=0x12ab990, return_value=0x7fffdb2e1000,
    instance=0x12ad020, args_list=<optimized out>, marshal_data=0x7fb2d65b7d70 <dbus_server_run_server>,
    n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.34.1/./gobject/gclosure.c:1550
#17 0x00007fb2d5e85407 in _g_closure_invoke_va (closure=0x12ab990, return_value=0x7fffdb2e1000,
    instance=0x12ad020, args=0x7fffdb2e11a8, n_params=0, param_types=0x0)
    at /build/buildd/glib2.0-2.34.1/./gobject/gclosure.c:840
#18 0x00007fb2d5e9ddf6 in g_signal_emit_valist (instance=0x12ad020, signal_id=<optimized out>, detail=0,
    var_args=var_args@entry=0x7fffdb2e11a8) at /build/buildd/glib2.0-2.34.1/./gobject/gsignal.c:3211
#19 0x00007fb2d5e9e642 in g_signal_emit (instan...

It's actually stuck inside the g_hash_table_lookup_node function.

could someone from the desktop team explain the reason why lightdm uses the evo calendar factory at all ? does not really seem necessary for spawning a greeter ...

@ogra: it doesn't use e-d-s, my guess is that the unity-greeter trigger it start through indicator-datetime which is loaded to have the time displayed on the greeter ... the greeter mode of the indicator should perhaps be hacked to not use e-d-s at all there

I'm finding this on my 12.04 LTS - it started about two weeks ago. It also seems to be sending and receiving data on the internet whether Evo is running or not. NetHogs listed it as the culprit.

Same issue here!! Sometimes it takes 333% CPU.