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 637396 - Hang when moving folders from mbox account to the new default maildir account
Hang when moving folders from mbox account to the new default maildir account
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Mailer
3.0.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[maildir]
Depends on:
Blocks:
 
 
Reported: 2010-12-16 16:02 UTC by Kjartan Maraas
Modified: 2013-09-14 16:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kjartan Maraas 2010-12-16 16:02:55 UTC
0x001b8424 in __kernel_vsyscall ()
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/lib/libgobject-2.0.so.0.2704.0-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
Missing separate debuginfos, use: debuginfo-install ibus-gtk2-1.3.99.20101202-1.fc15.i686 ibus-libs-1.3.99.20101202-1.fc15.i686
(gdb) bt
  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_lock_791
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 g_static_rec_mutex_lock
    at gthread.c line 1424
  • #5 camel_folder_summary_lock
    at camel-folder-summary.c line 4846
  • #6 message_info_from_uid
    at camel-folder-summary.c line 1249
  • #7 camel_folder_summary_uid
    at camel-folder-summary.c line 1315
  • #8 folder_get_message_info
    at camel-folder.c line 753
  • #9 camel_folder_get_message_info
    at camel-folder.c line 2190
  • #10 e_mail_reader_check_state
    at e-mail-reader.c line 3768
  • #11 mail_shell_view_update_actions
    at e-mail-shell-view.c line 880
  • #12 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 79
  • #13 g_type_class_meta_marshal
  • #14 g_closure_invoke
    at gclosure.c line 766
  • #15 signal_emit_unlocked_R
    at gsignal.c line 3182
  • #16 g_signal_emit_valist
    at gsignal.c line 2983
  • #17 g_signal_emit
    at gsignal.c line 3040
  • #18 e_shell_view_update_actions
    at e-shell-view.c line 1712
  • #19 mail_shell_view_folder_tree_selected_cb
    at e-mail-shell-view-private.c line 58
  • #20 e_marshal_VOID__STRING_STRING_UINT
    at e-marshal.c line 2340
  • #21 g_closure_invoke
  • #22 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #23 g_signal_emit_valist
    at gsignal.c line 2983
  • #24 g_signal_emit
    at gsignal.c line 3040
  • #25 folder_tree_selection_changed_cb
    at em-folder-tree.c line 706
  • #26 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 79
  • #27 g_closure_invoke
    at gclosure.c line 766
  • #28 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #29 g_signal_emit_valist
    at gsignal.c line 2983
  • #30 g_signal_emit
  • #31 _gtk_tree_selection_internal_select_node
    at gtktreeselection.c line 1427
  • #32 gtk_tree_view_real_set_cursor
    at gtktreeview.c line 12588
  • #33 gtk_tree_view_button_press
    at gtktreeview.c line 2794
  • #34 folder_tree_button_press_event
    at em-folder-tree.c line 882
  • #35 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 86
  • #36 g_type_class_meta_marshal
    at gclosure.c line 877
  • #37 g_closure_invoke
    at gclosure.c line 766
  • #38 signal_emit_unlocked_R
    at gsignal.c line 3290
  • #39 g_signal_emit_valist
  • #40 g_signal_emit
    at gsignal.c line 3040
  • #41 gtk_widget_event_internal
    at gtkwidget.c line 4995
  • #42 IA__gtk_propagate_event
    at gtkmain.c line 2461
  • #43 IA__gtk_main_do_event
    at gtkmain.c line 1627
  • #44 gdk_event_dispatch
    at gdkevents-x11.c line 2377
  • #45 g_main_dispatch
    at gmain.c line 2436
  • #46 g_main_context_dispatch
    at gmain.c line 3009
  • #47 g_main_context_iterate
    at gmain.c line 3087
  • #48 g_main_loop_run
    at gmain.c line 3295
  • #49 IA__gtk_main
    at gtkmain.c line 1238
  • #50 main
    at main.c line 697

Comment 1 Kjartan Maraas 2010-12-16 16:26:11 UTC
Another hang. This time when opening a folder for the first time after having moved it to maildir:

0x0082c424 in __kernel_vsyscall ()
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/lib/libgobject-2.0.so.0.2704.0-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
Missing separate debuginfos, use: debuginfo-install ibus-gtk2-1.3.99.20101202-1.fc15.i686 ibus-libs-1.3.99.20101202-1.fc15.i686
(gdb) bt
  • #0 __kernel_vsyscall
  • #1 write
    from /lib/libc.so.6
  • #2 _IO_new_file_write
    from /lib/libc.so.6
  • #3 new_do_write
    from /lib/libc.so.6
  • #4 _IO_new_do_write
    from /lib/libc.so.6
  • #5 _IO_new_file_overflow
    from /lib/libc.so.6
  • #6 _IO_new_file_xsputn
    from /lib/libc.so.6
  • #7 vfprintf
    from /lib/libc.so.6
  • #8 __printf_chk
    from /lib/libc.so.6
  • #9 printf
    at /usr/include/bits/stdio2.h line 105
  • #10 camel_debug_start
    at camel-debug.c line 128
  • #11 camel_store_get_folder_info_sync
    at camel-store.c line 2338
  • #12 update_actions_cb
    at templates.c line 790
  • #13 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 79
  • #14 g_closure_invoke
    at gclosure.c line 766
  • #15 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #16 g_signal_emit_valist
    at gsignal.c line 2983
  • #17 g_signal_emit
    at gsignal.c line 3040
  • #18 e_shell_view_update_actions
    at e-shell-view.c line 1712
  • #19 mail_shell_view_folder_tree_selected_cb
    at e-mail-shell-view-private.c line 58
  • #20 e_marshal_VOID__STRING_STRING_UINT
    at e-marshal.c line 2340
  • #21 g_closure_invoke
    at gclosure.c line 766
  • #22 signal_emit_unlocked_R
  • #23 g_signal_emit_valist
    at gsignal.c line 2983
  • #24 g_signal_emit
    at gsignal.c line 3040
  • #25 folder_tree_selection_changed_cb
    at em-folder-tree.c line 706
  • #26 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 79
  • #27 g_closure_invoke
    at gclosure.c line 766
  • #28 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #29 g_signal_emit_valist
    at gsignal.c line 2983
  • #30 g_signal_emit
    at gsignal.c line 3040
  • #31 _gtk_tree_selection_internal_select_node
    at gtktreeselection.c line 1427
  • #32 gtk_tree_view_real_set_cursor
    at gtktreeview.c line 12588
  • #33 gtk_tree_view_button_press
    at gtktreeview.c line 2794
  • #34 folder_tree_button_press_event
    at em-folder-tree.c line 882
  • #35 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 86
  • #36 g_type_class_meta_marshal
    at gclosure.c line 877
  • #37 g_closure_invoke
    at gclosure.c line 766
  • #38 signal_emit_unlocked_R
    at gsignal.c line 3290
  • #39 g_signal_emit_valist
  • #40 g_signal_emit
    at gsignal.c line 3040
  • #41 gtk_widget_event_internal
    at gtkwidget.c line 4995
  • #42 IA__gtk_propagate_event
    at gtkmain.c line 2461
  • #43 IA__gtk_main_do_event
    at gtkmain.c line 1627
  • #44 gdk_event_dispatch
    at gdkevents-x11.c line 2377
  • #45 g_main_dispatch
    at gmain.c line 2436
  • #46 g_main_context_dispatch
    at gmain.c line 3009
  • #47 g_main_context_iterate
    at gmain.c line 3087
  • #48 g_main_loop_run
    at gmain.c line 3295
  • #49 IA__gtk_main
    at gtkmain.c line 1238
  • #50 main
    at main.c line 697

Comment 2 Matthew Barnes 2010-12-16 16:48:59 UTC
It's hard to debug deadlocks without seeing traces for all the threads.

Can you capture a full trace with "thread apply all bt" instead of just "bt" please?
Comment 3 Matthew Barnes 2011-02-02 16:33:11 UTC
Removing GNOME 3.0 target since there's not enough information here to do anything.
Comment 4 Kjartan Maraas 2011-02-02 20:19:05 UTC
Could this possibly have happened because gnome-terminal ran out of file descriptors? There was a fd leak in g-t at the time I ran these things and I had CAMEL_DEBUG=all running in the terminal...
Comment 5 Matthew Barnes 2011-02-02 20:27:26 UTC
That's possible.  We may also be leaking file descriptors -- it's happened before.

If you can still reproduce this, a complete backtrace should all threads would be really helpful.
Comment 6 Matthew Barnes 2011-02-02 20:27:46 UTC
*showing all threads
Comment 7 Kjartan Maraas 2011-02-03 12:02:26 UTC
I tried moving a folder with 35k messages from mbox to maildir now without having any problems. Had enabled CAMEL_DEBUG=all in the terminal window during the move too.