GNOME Bugzilla – Bug 535075
Evolution cpu reaches 100% during import
Last modified: 2009-02-09 07:05:20 UTC
Evolution 2.22.1.1 (Group wise back end) I was importing around 2000 contact in an address book, when i looked in 'top' command output, evolution showed 100% cpu consumption. Gdb traces of evolution process Program received signal SIGINT, Interrupt. [Switching to Thread 0xb651a720 (LWP 24960)] 0xb7ceab19 in e_contact_get_const (contact=0x93268a8, field_id=E_CONTACT_FILE_AS) at e-contact.c:1569 1569 e-contact.c: No such file or directory. in e-contact.c (gdb) thread a a bt
+ Trace 198757
Thread 1 (Thread 0xb651a720 (LWP 24960))
Moved around 2150 contacts from personal address book to an address book of group back end (manually created) , just near completion evolution cpu consumption reached to 100%. Traces look same to previous one so pasting here. Program received signal SIGINT, Interrupt. [Switching to Thread 0xb64a7720 (LWP 30935)] 0xb67a40b2 in malloc_check (sz=28, caller=0xb68e3584) at hooks.c:266 266 hooks.c: No such file or directory. in hooks.c (gdb) thread a a bt
+ Trace 198842
Thread 1 (Thread 0xb64a7720 (LWP 30935))
Gdb traces of eds process at the same moment (evolution-data-server-2.22:30927): libecalbackendgroupwise-WARNING **: Failed to read the attachment from the server [New Thread 0xad0a6b90 (LWP 31692)] libedata-book-Message: Flushed summary to disk [Thread 0xad0a6b90 (LWP 31692) exited] [Thread 0xb08f6b90 (LWP 31418) exited] [Thread 0xb4140b90 (LWP 31414) exited] libedata-book-Message: Flushed summary to disk ^C Program received signal SIGINT, Interrupt. [Switching to Thread 0xb6ec66e0 (LWP 30927)] 0xffffe430 in __kernel_vsyscall () (gdb) thread a abt (gdb) thread a a bt
+ Trace 198843
It's trying to find the right position of the new contact in the list. It could take some time, and CPU usage, yes. Is it taking a long time? Is it doing similar thing when only opening that huge address book in a view?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!