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 720252 - Random freeze in 3.10.2
Random freeze in 3.10.2
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
3.10.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-12-11 13:08 UTC by André Klapper
Modified: 2015-01-17 03:16 UTC
See Also:
GNOME target: ---
GNOME version: 3.9/3.10



Description André Klapper 2013-12-11 13:08:04 UTC
No idea - was going through a GMail subfolder.

evolution-data-server-3.10.2-2.fc20.scratch2.i686
evolution-3.10.2-2.fc20.i686


$:andre\> gdb -p 2462
0xb778b424 in __kernel_vsyscall ()
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/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
(gdb) thread apply all bt

Thread 1 (Thread 0xb0f54900 (LWP 2462))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    at ../nptl/sysdeps/unix/sysv/linux/i386/i486/lowlevellock.S line 144
  • #2 _L_lock_829
    from /lib/libpthread.so.0
  • #3 __GI___pthread_mutex_lock
    at ../nptl/pthread_mutex_lock.c line 114
  • #4 g_rec_mutex_lock
    at gthread-posix.c line 382
  • #5 camel_folder_summary_lock
  • #6 message_info_from_uid
    at camel-folder-summary.c line 1895
  • #7 camel_folder_summary_get
    at camel-folder-summary.c line 1977
  • #8 folder_get_message_info
    at camel-folder.c line 883
  • #9 camel_folder_get_message_info
    at camel-folder.c line 2583
  • #10 e_mail_reader_check_state
    at e-mail-reader.c line 4006
  • #11 mail_shell_view_update_actions
    at e-mail-shell-view.c line 885
  • #12 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 85
  • #13 g_type_class_meta_marshal
    at gclosure.c line 970
  • #14 g_closure_invoke
    at gclosure.c line 777
  • #15 signal_emit_unlocked_R
    at gsignal.c line 3516
  • #16 g_signal_emit_valist
    at gsignal.c line 3330
  • #17 g_signal_emit
    at gsignal.c line 3386
  • #18 e_shell_view_update_actions
    at e-shell-view.c line 1838
  • #19 shell_view_call_update_actions_idle
    at e-shell-view.c line 1850
  • #20 g_idle_dispatch
    at gmain.c line 5251
  • #21 g_main_dispatch
    at gmain.c line 3066
  • #22 g_main_context_dispatch
    at gmain.c line 3642
  • #23 g_main_context_iterate
    at gmain.c line 3713
  • #24 g_main_loop_run
    at gmain.c line 3907
  • #25 gtk_main
    at gtkmain.c line 1158
  • #26 main
    at main.c line 683

(gdb) list
411	
412		g_object_unref (settings);
413	
414		return shell;
415	}
416	
417	gint
418	main (gint argc,
419	      gchar **argv)
420	{
(gdb)
Comment 1 Matthew Barnes 2013-12-11 14:24:20 UTC
Stuck waiting to lock the folder summary mutex.  Can't tell from the backtrace what else had it locked already.  Maybe thread 2?

I'm working on fixing Camel's mutex abuses for 3.12, but the folder summary is going to be particularly nasty.  Until then, we'll likely continue as we always have with these intermittent lock ups.
Comment 2 André Klapper 2014-01-02 12:22:35 UTC
Was going through IMAP mail inbox subfolder; Evolution froze; switching and going back just displays a grey window.

evolution-3.10.3-1.fc20.i686
evolution-data-server-3.10.3-1.fc20.scratch1.i686



(gdb) thread apply all bt

Thread 1 (Thread 0xb0f91900 (LWP 3054))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    at ../nptl/sysdeps/unix/sysv/linux/i386/i486/lowlevellock.S line 144
  • #2 _L_lock_829
    from /lib/libpthread.so.0
  • #3 __GI___pthread_mutex_lock
    at ../nptl/pthread_mutex_lock.c line 114
  • #4 g_rec_mutex_lock
    at gthread-posix.c line 382
  • #5 camel_folder_summary_lock
    at camel-folder-summary.c line 4955
  • #6 message_info_from_uid
    at camel-folder-summary.c line 1895
  • #7 camel_folder_summary_get
    at camel-folder-summary.c line 1977
  • #8 folder_get_message_info
    at camel-folder.c line 883
  • #9 camel_folder_get_message_info
    at camel-folder.c line 2583
  • #10 e_mail_reader_check_state
    at e-mail-reader.c line 4006
  • #11 mail_shell_view_update_actions
    at e-mail-shell-view.c line 897
  • #12 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 85
  • #13 g_type_class_meta_marshal
    at gclosure.c line 970
  • #14 g_closure_invoke
    at gclosure.c line 777
  • #15 signal_emit_unlocked_R
    at gsignal.c line 3516
  • #16 g_signal_emit_valist
    at gsignal.c line 3330
  • #17 g_signal_emit
    at gsignal.c line 3386
  • #18 e_shell_view_update_actions
    at e-shell-view.c line 1838
  • #19 shell_view_call_update_actions_idle
    at e-shell-view.c line 1850
  • #20 g_idle_dispatch
    at gmain.c line 5251
  • #21 g_main_dispatch
    at gmain.c line 3066
  • #22 g_main_context_dispatch
    at gmain.c line 3642
  • #23 g_main_context_iterate
    at gmain.c line 3713
  • #24 g_main_loop_run
    at gmain.c line 3907
  • #25 gtk_main
    at gtkmain.c line 1158
  • #26 main
    at main.c line 683

Comment 3 André Klapper 2014-01-08 18:50:52 UTC
My status bar says "Retrieving message '123456' in foldername (cancelling)" for 30 min or so, happily ignored any Stop buttons being clicked, or whether I successfully went offline in Evolution. Continuing to do some work, Evo at some point froze. After 5 min I gave up and attached gdb to it.


0xb77e8424 in __kernel_vsyscall ()
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/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
(gdb) thread apply all bt

Thread 1 (Thread 0xb0fab900 (LWP 24895))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    at ../nptl/sysdeps/unix/sysv/linux/i386/i486/lowlevellock.S line 144
  • #2 _L_lock_829
    from /lib/libpthread.so.0
  • #3 __GI___pthread_mutex_lock
    at ../nptl/pthread_mutex_lock.c line 114
  • #4 g_rec_mutex_lock
    at gthread-posix.c line 382
  • #5 camel_folder_summary_lock
    at camel-folder-summary.c line 4955
  • #6 message_info_from_uid
    at camel-folder-summary.c line 1895
  • #7 camel_folder_summary_get
    at camel-folder-summary.c line 1977
  • #8 folder_get_message_user_tag
    at camel-folder.c line 770
  • #9 camel_folder_get_message_user_tag
  • #10 mail_shell_view_update_label_action
    at e-mail-shell-view-actions.c line 2255
  • #11 e_mail_shell_view_update_popup_labels
    at e-mail-shell-view-actions.c line 2355
  • #12 mail_shell_view_update_actions
    at e-mail-shell-view.c line 1071
  • #13 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 85
  • #14 g_type_class_meta_marshal
    at gclosure.c line 970
  • #15 g_closure_invoke
    at gclosure.c line 777
  • #16 signal_emit_unlocked_R
    at gsignal.c line 3516
  • #17 g_signal_emit_valist
    at gsignal.c line 3330
  • #18 g_signal_emit
    at gsignal.c line 3386
  • #19 e_shell_view_update_actions
    at e-shell-view.c line 1838
  • #20 shell_view_call_update_actions_idle
    at e-shell-view.c line 1850
  • #21 g_idle_dispatch
    at gmain.c line 5251
  • #22 g_main_dispatch
    at gmain.c line 3066
  • #23 g_main_context_dispatch
    at gmain.c line 3642
  • #24 g_main_context_iterate
    at gmain.c line 3713
  • #25 g_main_loop_run
    at gmain.c line 3907
  • #26 gtk_main
    at gtkmain.c line 1158
  • #27 main
    at main.c line 683
411	
412		g_object_unref (settings);
413	
414		return shell;
415	}
416	
417	gint
418	main (gint argc,
419	      gchar **argv)
420	{
(gdb) info registers
eax            0xfffffe00	-512
ecx            0x80	128
edx            0x2	2
ebx            0xa30c1078	-1559490440
esp            0xbf827fe0	0xbf827fe0
ebp            0xf56b8f0	0xf56b8f0
esi            0x0	0
edi            0x0	0
eip            0xb77e8424	0xb77e8424 <__kernel_vsyscall+16>
eflags         0x200202	[ IF ID ]
cs             0x73	115
ss             0x7b	123
ds             0x7b	123
es             0x7b	123
fs             0x0	0
gs             0x33	51
(gdb) quit
A debugging session is active.

	Inferior 1 [process 24895] will be detached.

Quit anyway? (y or n) y
Detaching from program: /usr/bin/evolution, process 24895
$:andre\> fuckevo 

** (evolution:340): CRITICAL **: categories_icon_theme_hack: assertion 'filename != NULL && *filename != '\0'' failed
No response from Evolution -- killing the process
$:andre\> rpm -q evolution
evolution-3.10.3-1.fc20.i686
$:andre\> rpm -q evolution-data-server
evolution-data-server-3.10.3-1.fc20.scratch1.i686
$:andre\> fuckevo 

** (evolution:368): CRITICAL **: categories_icon_theme_hack: assertion 'filename != NULL && *filename != '\0'' failed

(evolution:368): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
Evolution process exited normally
$:andre\> fuckevo 
Could not find Evolution's process ID
$:andre\>
Comment 4 André Klapper 2015-01-17 03:16:51 UTC
Not seen again yet in 3.12; assuming this is fixed.