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 618234 - crash in evolution mailer
crash in evolution mailer
Status: RESOLVED DUPLICATE of bug 619716
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-05-10 08:30 UTC by Frederic Crozat
Modified: 2010-11-12 05:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Frederic Crozat 2010-05-10 08:30:08 UTC 
I got the following crash in evolution 2.30.1.2 / e-d-s 2.30.1 :

(gdb) thread apply all bt

+ Trace 221836

Thread 1 (Thread 0xb64ff7e0 (LWP 21976))

  • #0 magazine_chain_pop_head
    at gslice.c line 486
  • #1 thread_memory_magazine1_alloc
    at gslice.c line 789
  • #2 IA__g_slice_alloc
    at gslice.c line 827
  • #3 IA__g_slist_prepend
    at gslist.c line 273
  • #4 copy_value_list
    at gconf-value.c line 703
  • #5 gconf_value_copy
    at gconf-value.c line 746
  • #6 gconf_entry_new
    at gconf-value.c line 1447
  • #7 gconf_entry_copy
    at gconf-value.c line 1510
  • #8 get
    at gconf-client.c line 1271
  • #9 gconf_client_get_full
    at gconf-client.c line 1326
  • #10 gconf_client_get_list
    at gconf-client.c line 1629
  • #11 load_from_gconf
    at e-source-list.c line 73
  • #12 e_source_list_new_for_gconf
    at e-source-list.c line 368
  • #13 e_book_get_addressbooks
    at e-book.c line 2202
  • #14 e_name_selector_entry_init
    at e-name-selector-entry.c line 2665
  • #15 IA__g_type_create_instance
    at gtype.c line 1877
  • #16 g_object_constructor
    at gobject.c line 1396
  • #17 IA__g_object_newv
    at gobject.c line 1261
  • #18 IA__g_object_new
    at gobject.c line 1092
  • #19 e_name_selector_list_new
    at e-name-selector-list.c line 660
  • #20 e_name_selector_peek_section_list
    at e-name-selector.c line 392
  • #21 composer_name_header_constructor
    at e-composer-name-header.c line 136
  • #22 IA__g_object_newv
    at gobject.c line 1261
  • #23 IA__g_object_new_valist
    at gobject.c line 1377
  • #24 IA__g_object_new
    at gobject.c line 1095
  • #25 e_composer_name_header_new_with_label
    at e-composer-name-header.c line 304
  • #26 composer_header_table_init
    at e-composer-header-table.c line 972
  • #27 IA__g_type_create_instance
    at gtype.c line 1885
  • #28 g_object_constructor
    at gobject.c line 1396
  • #29 composer_header_table_constructor
    at e-composer-header-table.c line 495
  • #30 IA__g_object_newv
    at gobject.c line 1180
  • #31 IA__g_object_new
    at gobject.c line 1092
  • #32 e_composer_header_table_new
    at e-composer-header-table.c line 1050
  • #33 e_composer_private_constructed
    at e-composer-private.c line 243
  • #34 msg_composer_constructed
    at e-msg-composer.c line 1636
  • #35 IA__g_object_newv
    at gobject.c line 1289
  • #36 IA__g_object_new_valist
    at gobject.c line 1377
  • #37 IA__g_object_new
    at gobject.c line 1095
  • #38 e_msg_composer_new
    at e-msg-composer.c line 2194
  • #39 reply_get_composer
    at em-composer-utils.c line 1704
  • #40 em_utils_reply_to_message
    at em-composer-utils.c line 2276
  • #41 reply_to_message
    at em-composer-utils.c line 2201
  • #42 get_message_done
    at mail-ops.c line 1865
  • #43 mail_msg_idle_cb
    at mail-mt.c line 453
  • #44 g_idle_dispatch
    at gmain.c line 4065
  • #45 g_main_dispatch
    at gmain.c line 1960
  • #46 IA__g_main_context_dispatch
    at gmain.c line 2513
  • #47 g_main_context_iterate
    at gmain.c line 2591
  • #48 IA__g_main_loop_run
    at gmain.c line 2799
  • #49 IA__gtk_main
    at gtkmain.c line 1219
  • #50 main
    at main.c line 578 






Comment 1


Akhil Laddha





          2010-05-10 08:43:17 UTC
        



any steps or operation where you got the crash ?






Comment 2


Frederic Crozat





          2010-05-10 09:48:57 UTC
        



I just had pressed Ctrl-L to reply to a mail and I guess imapx backend was running at the same time refreshing my folders. Not reproducible unfortunately.






Comment 3


Frederic Crozat





          2010-05-10 12:55:47 UTC
        



just got the same crash when pressing Ctrl-L and waiting for composer to open :



Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xacdffb70 (LWP 21498)]
magazine_chain_pop_head (ix=<value optimized out>, magazine_chunks=0x5e0, 
    count=7) at gslice.c:486
486	      (*magazine_chunks)->data = chunk->next;
(gdb) thread apply all bt





+
Trace
    221842






Thread 1
          (Thread 0xb64ff7e0 (LWP 2016))


    

  • 
#0
unique_app_get_type

    
                at ./uniqueapp.c
                  line
                  75

    

    • 

  • 
#1
e_shell_watch_window

    
                at e-shell.c
                  line
                  1473

    

    • 

  • 
#2
msg_composer_constructed

    
                at e-msg-composer.c
                  line
                  1646

    

    • 

  • 
#3
IA__g_object_newv

    
                at gobject.c
                  line
                  1289

    

    • 

  • 
#4
IA__g_object_new_valist

    
                at gobject.c
                  line
                  1377

    

    • 

  • 
#5
IA__g_object_new

    
                at gobject.c
                  line
                  1095

    

    • 

  • 
#6
e_msg_composer_new

    
                at e-msg-composer.c
                  line
                  2194

    

    • 

  • 
#7
reply_get_composer

    
                at em-composer-utils.c
                  line
                  1704

    

    • 

  • 
#8
em_utils_reply_to_message

    • 

  • 
#9
reply_to_message

    
                at em-composer-utils.c
                  line
                  2201

    

    • 

  • 
#10
get_message_done

    
                at mail-ops.c
                  line
                  1865

    

    • 

  • 
#11
mail_msg_idle_cb

    
                at mail-mt.c
                  line
                  453

    

    • 

  • 
#12
g_idle_dispatch

    
                at gmain.c
                  line
                  4065

    

    • 

  • 
#13
g_main_dispatch

    
                at gmain.c
                  line
                  1960

    

    • 

  • 
#14
IA__g_main_context_dispatch

    
                at gmain.c
                  line
                  2513

    

    • 

  • 
#15
g_main_context_iterate

    
                at gmain.c
                  line
                  2591

    

    • 

  • 
#16
IA__g_main_loop_run

    
                at gmain.c
                  line
                  2799

    

    • 

  • 
#17
IA__gtk_main

    
                at gtkmain.c
                  line
                  1219

    

    • 

  • 
#18
main

    
                at main.c
                  line
                  578

    

    • 













Comment 4


Milan Crha





          2010-10-01 11:54:13 UTC
        



Could you run evolution like this and try to reproduce the issue, please?
   $ G_SLICE=always-malloc evolution

It should claim something. But if it wouldn't even after few tries, then maybe use valgrind for a memory checking, like the following command, though evolution use to be quite slow under valgrind:
   $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>evo.log

Thanks in advance.






Comment 5


Frederic Crozat





          2010-10-01 14:07:50 UTC
        



I won't be able to duplicate this, since the system I was using was in my previous employer and I switched both company and distributions :(






Comment 6


Akhil Laddha





          2010-11-12 05:17:42 UTC
        




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