GNOME Bugzilla – Bug 705706
When searching EWS contacts the UI blocks
Last modified: 2014-03-10 17:48:23 UTC
I have an EWS account on an Exchange Server with a fairly large contact list. When searching for contacts in the "Select Contacts From Address Book" dialog (as a result of pressing the "To:" or "CC:" labels in the composer) the search blocks the UI of all open Evolution windows. The threaded stack trace looks like (apologies in advance but I'm not sure how the Fedora abrt/etc. system installs debuginfo packages in /var/cache/abrt-di and how I can achieve the same outside of abrt -- and I don't want to duplicate that effort by using yum/rpm to install debuginfo packages):
+ Trace 232363
Thread 1 (Thread 0x7fac84ae5a40 (LWP 2899))
Oh, and what looks nasty is that after the UI unblocks, pressumably because the search is done, it blocks again, (for minutes at a time BTW) for updates to the search box. Quite unusable in fact with 100K contacts, even when they are locally cached -- which I understand they are supposed to be.
Ahhh. Seems like I might have figured out how to utilize /var/cache/abrt-di:
+ Trace 232364
With evolution using >99% of a core.
Please install debug packages for glib2, evolution, evolution-data-server and paste a new stacktrace here. You can also use "gdb" and enter "thread apply all bt" instead of copying from abrt.
Unfortunately 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!
I think I have the trace you are looking for: Attaching to program: /usr/bin/evolution, process 24538 [New LWP 25697] [New LWP 24798] [New LWP 24706] [New LWP 24678] [New LWP 24654] [New LWP 24644] [New LWP 24643] [New LWP 24642] [New LWP 24641] [New LWP 24640] [New LWP 24639] [New LWP 24638] [New LWP 24608] [New LWP 24607] [New LWP 24544] [New LWP 24543] [New LWP 24542] [New LWP 24541] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace 0x0000003343261bd7 in node_get_next (node=0xd35c600) at gsequence.c:1623 1623 gsequence.c: No such file or directory.
+ Trace 233278
Thread 1 (Thread 0x7fe3d625ca80 (LWP 24538))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 630504 ***