After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 740688 - Evolution locks up when addressbook updates
Evolution locks up when addressbook updates
Status: RESOLVED DUPLICATE of bug 629510
Product: evolution
Classification: Applications
Component: Contacts
3.12.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-11-25 14:07 UTC by David Woodhouse
Modified: 2014-11-27 12:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Woodhouse 2014-11-25 14:07:03 UTC 
My EWS addressbook just updated itself in the background:

GAL update completed successfully in 43742652 µs. Added: 121, Changed: 340, Unchanged 245148, Removed: 94


Now Evolution has stopped responding. I was typing an email and it's just doing nothing. The main thread is off in the weeds, for several minutes...

(gdb) bt

+ Trace 234370

  • #0 __strcmp_ssse3
    at ../sysdeps/x86_64/strcmp.S line 211
  • #1 esort_callback
  • #2 msort_with_tmp
  • #3 msort_with_tmp
  • #4 msort_r
  • #5 sorter_array_sort.part
  • #6 sorter_array_backsort.part
  • #7 sorter_array_model_to_sorted
  • #8 items_inserted
  • #9 g_closure_invoke
  • #10 signal_emit_unlocked_R
  • #11 g_signal_emit_valist
  • #12 g_signal_emit
  • #13 g_closure_invoke
  • #14 signal_emit_unlocked_R
  • #15 g_signal_emit_valist
  • #16 g_signal_emit
  • #17 view_create_contact_cb
  • #18 g_cclosure_marshal_VOID__POINTERv
  • #19 _g_closure_invoke_va
  • #20 g_signal_emit_valist
  • #21 g_signal_emit
  • #22 book_client_view_emit_objects_added_idle_cb
  • #23 g_main_context_dispatch
  • #24 g_main_context_iterate.isra
  • #25 g_main_loop_run
  • #26 gtk_main
  • #27 main 






Comment 1


Milan Crha





          2014-11-27 08:41:08 UTC
        



Thanks for a bug report. I believe this is a variant of bug #629510. Tristan's cursors should make this work sanely, but there is currently no man power to turn it into action (and code). I'd close this as a duplicate of bug #629510, if you do not mind.






Comment 2


David Woodhouse





          2014-11-27 10:57:10 UTC
        



Thanks. This was probably triggered when I fixed the EWS backend to actually do the notifications consistently on the GAL. I wonder if I should revert that, given that we've *never* noticed things being out of sync, and we *do* notice when Evolution stops responding.

On the plus side, I *did* also implement cursor support for EWS... although there are other back ends which don't support it and would probably need to be fixed before we could even consider updating Evolution to use them.






Comment 3


Milan Crha





          2014-11-27 12:52:13 UTC
        



(In reply to comment #2)
> although there are other back ends which don't support it and would probably
> need to be fixed before we could even consider updating Evolution to use them.

Yes, that's the other side why this is postponed. I'd create a "Meta" backend first, adapt all in-house backends to it, and only then start to play with evolution itself. The Meta backend will provide things from which the UI application can benefit in a way which will not duplicate the code across the backends.

*** This bug has been marked as a duplicate of bug 629510 ***