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 682281 - SIGSEGV in camel_folder_search_search (camel-folder-search.c:666)
SIGSEGV in camel_folder_search_search (camel-folder-search.c:666)
Status: RESOLVED DUPLICATE of bug 680467
Product: evolution
Classification: Applications
Component: Mailer
3.6.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-08-20 17:15 UTC by David Ronis
Modified: 2013-09-13 01:09 UTC
See Also:
GNOME target: ---
GNOME version: 3.5/3.6


Description David Ronis 2012-08-20 17:15:12 UTC 
I was browsing my e-mail with this morning's git/master of evo and related programs.   I was deleting, individually, about 8 consecutive e-mails, basically, rapid-fire clicks on the delete button 

Here's the backtrace:

+ Trace 230709

Thread 16 (Thread 0x85b3bb70 (LWP 11863))

  • #0 __lll_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_lock_994
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 g_mutex_lock
    at gthread-posix.c line 208
  • #4 local_folder_search_free
    at camel-local-folder.c line 296
  • #5 camel_folder_search_free
    at camel-folder.c line 2774
  • #6 vee_folder_subfolder_changed
    at camel-vee-folder.c line 464
  • #7 vee_folder_process_changes
    at camel-vee-folder.c line 499
  • #8 session_do_job_cb
    at camel-session.c line 175
  • #9 run_in_thread
    at gsimpleasyncresult.c line 869
  • #10 io_job_thread
    at gioscheduler.c line 162
  • #11 g_thread_pool_thread_proxy
    at gthreadpool.c line 309
  • #12 g_thread_proxy
    at gthread.c line 801
  • #13 start_thread
    from /lib/libpthread.so.0
  • #14 clone
    from /lib/libc.so.6

Thread 14 (Thread 0xb0d7f880 (LWP 11717))

  • #0 g_hash_table_maybe_resize
    at ghash.c line 629
  • #1 g_hash_table_remove_all
    at ghash.c line 1346
  • #2 gtk_style_context_clear_cache
    at gtkstylecontext.c line 2925
  • #3 gtk_style_context_invalidate
    at gtkstylecontext.c line 3190
  • #4 _gtk_style_context_queue_invalidate
    at gtkstylecontext.c line 3168
  • #5 gtk_style_context_cascade_changed
    at gtkstylecontext.c line 666
  • #6 gtk_style_context_set_cascade
    at gtkstylecontext.c line 700
  • #7 g_type_create_instance
    at gtype.c line 1890
  • #8 g_object_constructor
    at gobject.c line 1854
  • #9 g_object_newv
    at gobject.c line 1637
  • #10 g_object_new
    at gobject.c line 1547
  • #11 gtk_style_context_new
    at gtkstylecontext.c line 1081
  • #12 gtk_widget_get_style_context
    at gtkwidget.c line 14003
  • #13 gtk_menu_item_init
    at gtkmenuitem.c line 489
  • #14 g_type_create_instance
    at gtype.c line 1882
  • #15 g_object_constructor
    at gobject.c line 1854
  • #16 g_object_newv
    at gobject.c line 1718
  • #17 g_object_new
    at gobject.c line 1547
  • #18 create_menu_item
    at gtkaction.c line 700
  • #19 gtk_action_create_menu_item
    at gtkaction.c line 917
  • #20 update_node
    at gtkuimanager.c line 2930
  • #21 update_node
    at gtkuimanager.c line 3096
  • #22 update_node
    at gtkuimanager.c line 3096
  • #23 update_node
    at gtkuimanager.c line 3096
  • #24 do_updates
    at gtkuimanager.c line 3138
  • #25 do_updates_idle
    at gtkuimanager.c line 3148
  • #26 gdk_threads_dispatch
    at gdk.c line 788
  • #27 g_idle_dispatch
    at gmain.c line 4797
  • #28 g_main_dispatch
    at gmain.c line 2707
  • #29 g_main_context_dispatch
    at gmain.c line 3211
  • #30 g_main_context_iterate
    at gmain.c line 3282
  • #31 g_main_loop_run
    at gmain.c line 3476
  • #32 gtk_main
    at gtkmain.c line 1162
  • #33 main
    at main.c line 674

Thread 11 (Thread 0x887ffb70 (LWP 11867))

  • #0 camel_vee_folder_get_type
    at camel-vee-folder.c line 85
  • #1 vee_folder_merge_matching
    at camel-vee-folder.c line 263
  • #2 vee_folder_subfolder_changed
    at camel-vee-folder.c line 457
  • #3 vee_folder_process_changes
    at camel-vee-folder.c line 499
  • #4 session_do_job_cb
    at camel-session.c line 175
  • #5 run_in_thread
    at gsimpleasyncresult.c line 869
  • #6 io_job_thread
    at gioscheduler.c line 162
  • #7 g_thread_pool_thread_proxy
    at gthreadpool.c line 309
  • #8 g_thread_proxy
    at gthread.c line 801
  • #9 start_thread
    from /lib/libpthread.so.0
  • #10 clone
    from /lib/libc.so.6

Thread 3 (Thread 0x88fffb70 (LWP 11844))

  • #0 __lll_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_lock_994
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 g_mutex_lock
    at gthread-posix.c line 208
  • #4 local_folder_search_by_uids
  • #5 camel_folder_search_by_uids
  • #6 vee_folder_subfolder_changed
    at camel-vee-folder.c line 445
  • #7 vee_folder_process_changes
    at camel-vee-folder.c line 499
  • #8 session_do_job_cb
    at camel-session.c line 175
  • #9 run_in_thread
    at gsimpleasyncresult.c line 869
  • #10 io_job_thread
    at gioscheduler.c line 162
  • #11 g_thread_pool_thread_proxy
    at gthreadpool.c line 309
  • #12 g_thread_proxy
    at gthread.c line 801
  • #13 start_thread
    from /lib/libpthread.so.0
  • #14 clone
    from /lib/libc.so.6

Thread 1 (Thread 0x81a6cb70 (LWP 11866))

  • #0 camel_folder_search_search
  • #1 local_folder_search_by_expression
  • #2 camel_folder_search_by_expression
  • #3 regen_list_exec
    at message-list.c line 4690
  • #4 mail_msg_proxy
    at mail-mt.c line 423
  • #5 g_thread_pool_thread_proxy
    at gthreadpool.c line 309
  • #6 g_thread_proxy
    at gthread.c line 801
  • #7 start_thread
    from /lib/libpthread.so.0
  • #8 clone
    from /lib/libc.so.6 






Comment 1


Milan Crha





          2012-08-20 19:26:29 UTC
        



Thanks for a bug report. This is basically bug #680467, thus I'm marking this as a duplicate of it.

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