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 356713 - Evolution crashes when opening a collapsed thread containing a recently received message
Evolution crashes when opening a collapsed thread containing a recently recei...
Status: RESOLVED DUPLICATE of bug 330728
Product: evolution
Classification: Applications
Component: Mailer
2.8.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-09-19 12:04 UTC by Oded Arbel
Modified: 2006-09-25 13:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Oded Arbel 2006-09-19 12:04:10 UTC 
Steps to reproduce:
1. Go to a folder (I use a non-INBOX folder on an IMAP - it might be reproducable under other conditions, but I'm not sure), open the "View" menu, enable threaded view and choose collapse all threads.
2. Select a message (it can be the top message of a thread or a standalone message).
3. Write a reply to the select message and mail it to yourself. I mail it to an address that causes the mail to be automatically filed (on the server) to the same folder, but it may be also reproducable when mailing to the INBOX and then doing move - I'll check in a minute.
4. After the mail has been sent, go to another folder, and wait for the mail to be delivered (Evolution should notify and increment the unread count on the original folder).
5. Go back to the original folder - the cursor should have the original message selected, and it should have a collapsed thread underneath. 
6. Open the thread - crash.


Stack trace:
Distribution: Fedora Core release 5.92 (FC6 Test3)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 241999872 vsize: 0 resident: 241999872 share: 0 rss: 33210368 rss_rlim: 0
CPU usage: start_time: 1158666965 rtime: 0 utime: 691 stime: 0 cutime:360 cstime: 0 timeout: 331 it_real_value: 0 frequency: 121

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208674608 (LWP 10003)]
[New Thread -1391031408 (LWP 10045)]
[New Thread -1380541552 (LWP 10042)]
[New Thread -1369449584 (LWP 10036)]
[New Thread -1348469872 (LWP 10034)]
[New Thread -1358959728 (LWP 10033)]
[New Thread -1300235376 (LWP 10029)]
[New Thread -1278198896 (LWP 10025)]
[New Thread -1289094256 (LWP 10024)]
[New Thread -1267709040 (LWP 10022)]
[New Thread -1257219184 (LWP 10021)]
[New Thread -1246729328 (LWP 10020)]
0xb7f8a402 in __kernel_vsyscall ()

+ Trace 72729

Thread 1 (Thread -1208674608 (LWP 10003))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 426
  • #4 <signal handler called>
  • #5 ect_check
    at gal-a11y-e-cell-text.c line 69
  • #6 ect_get_name
    at gal-a11y-e-cell-text.c line 81
  • #7 atk_object_get_name
    from /usr/lib/libatk-1.0.so.0
  • #8 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #9 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #10 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #13 atk_object_notify_state_change
    from /usr/lib/libatk-1.0.so.0
  • #14 gal_a11y_e_cell_add_state
    at gal-a11y-e-cell.c line 496
  • #15 ectr_model_row_changed_cb
    at gal-a11y-e-cell-tree.c line 46
  • #16 g_cclosure_marshal_VOID
    from /lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #21 e_table_model_row_changed
    at e-table-model.c line 487
  • #22 e_tree_table_adapter_node_set_expanded
    at e-tree-table-adapter.c line 1117
  • #23 animate_expander
    at e-cell-tree.c line 447
  • #24 g_source_get_current_time
    from /lib/libglib-2.0.so.0
  • #25 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #26 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #28 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #29 main
    at main.c line 615
  • #30 __libc_start_main
    from /lib/libc.so.6
  • #31 _start
  • #0 __kernel_vsyscall 


Other information:
I tried to submit the crash using BugBuddy, but it claimed that the application doesn't exist in the GNOME bugzilla.
Comment 1 Oded Arbel 2006-09-19 12:15:37 UTC 
I tried to reproduce the problem when the reply is not being filed to the same folder (server-side) but instead sent to INBOX and then I move it from the INBOX to the target folder - then go to the folder and uncollapse the thread, but I couldn't get the same behavior. 

Instead, if the message arrives and is marked unread (its marked unread if I select if for 3 seconds, and I can't move it fast enough because I have to hit CTRL-SHIFT-V and then scroll down to the target folder and click "Move"), then everything is ok. 

On the other hand, if I have the "Move message" dialog with the target folder already selected (because I moved something there previously), then I can move the message fast enough and it arrives unread on the target folder - in this case Evolution crashes immediately as I select the target folder - without even seeing the message list (if my machine is loaded when I select the folder then Evolution first selects the folder with an empty message list, then after a while it crashes - probably while trying to render the message list). Anyway - here's the backtrace of the other crash, which I think is related to the same problem:

Distribution: Fedora Core release 5.92 (FC6 Test3)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 291500032 vsize: 0 resident: 291500032 share: 0 rss: 37117952 rss_rlim: 0
CPU usage: start_time: 1158667619 rtime: 0 utime: 1206 stime: 0 cutime:994 cstime: 0 timeout: 212 it_real_value: 0 frequency: 282

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208285488 (LWP 10827)]
[New Thread -1380656240 (LWP 10893)]
[New Thread -1370166384 (LWP 10892)]
[New Thread -1358255216 (LWP 10861)]
[New Thread -1347765360 (LWP 10860)]
[New Thread -1299190896 (LWP 10855)]
[New Thread -1288701040 (LWP 10851)]
[New Thread -1277817968 (LWP 10850)]
[New Thread -1267319920 (LWP 10846)]
[New Thread -1256830064 (LWP 10845)]
[New Thread -1246340208 (LWP 10844)]
0xb7fe9402 in __kernel_vsyscall ()

+ Trace 72730

Thread 1 (Thread -1208285488 (LWP 10827))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 426
  • #4 <signal handler called>
  • #5 ect_check
    at gal-a11y-e-cell-text.c line 69
  • #6 ect_get_name
    at gal-a11y-e-cell-text.c line 81
  • #7 atk_object_get_name
    from /usr/lib/libatk-1.0.so.0
  • #8 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #9 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #10 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #13 atk_object_notify_state_change
    from /usr/lib/libatk-1.0.so.0
  • #14 gal_a11y_e_cell_remove_state
    at gal-a11y-e-cell.c line 525
  • #15 ectr_model_row_changed_cb
    at gal-a11y-e-cell-tree.c line 48
  • #16 g_cclosure_marshal_VOID
    from /lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #21 e_table_model_row_changed
    at e-table-model.c line 487
  • #22 e_tree_table_adapter_node_set_expanded
    at e-tree-table-adapter.c line 1117
  • #23 e_tree_table_adapter_load_expanded_state
    at e-tree-table-adapter.c line 1053
  • #24 e_tree_load_expanded_state
    at e-tree.c line 2010
  • #25 regen_list_regened
    at message-list.c line 1690
  • #26 mail_msgport_replied
    at mail-mt.c line 461
  • #27 g_io_channel_unix_get_fd
    from /lib/libglib-2.0.so.0
  • #28 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #29 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #31 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #32 main
    at main.c line 615
  • #33 __libc_start_main
    from /lib/libc.so.6
  • #34 _start
  • #0 __kernel_vsyscall 






Comment 2


Oded Arbel





          2006-09-19 12:29:44 UTC
        



I managed to reproduce the second crash on my INBOX (which is on IMAP) - same setup:
1. have "Group by threads" enabled
2. "Collapse all threads"
3. Reply to yourself (I think it works with external email as well
4. go to another folder.
5. wait for Evolution to receive the message (increment unread message count on the folder and notify).
6. Select the inbox again - crash.

Backtrace attached - its the same as the second backtrace above, except for some addresses. I'm wondering if I should open a different crash report for this behavior, but I have a feeling its related to the original crash and the stack trace is rather similar (I saw a 2 line difference in one stack frame on one thread).

Distribution: Fedora Core release 5.92 (FC6 Test3)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 257171456 vsize: 0 resident: 257171456 share: 0 rss: 38961152 rss_rlim: 0
CPU usage: start_time: 1158668216 rtime: 0 utime: 1529 stime: 0 cutime:1275 cstime: 0 timeout: 254 it_real_value: 0 frequency: 694

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208719664 (LWP 11639)]
[New Thread -1380861040 (LWP 11686)]
[New Thread -1370371184 (LWP 11683)]
[New Thread -1358959728 (LWP 11677)]
[New Thread -1348469872 (LWP 11676)]
[New Thread -1299629168 (LWP 11671)]
[New Thread -1289139312 (LWP 11667)]
[New Thread -1278248048 (LWP 11666)]
[New Thread -1267754096 (LWP 11664)]
[New Thread -1257264240 (LWP 11663)]
[New Thread -1246774384 (LWP 11662)]
0xb7f7f402 in __kernel_vsyscall ()




+
Trace
    72731






Thread 1
          (Thread -1208719664 (LWP 11639))


    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
__waitpid_nocancel

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#2
gnome_gtk_module_info_get

    
                from
                /usr/lib/libgnomeui-2.so.0

    

    • 

  • 
#3
segv_redirect

    
                at main.c
                  line
                  426

    

    • 

  • 
#4
<signal handler called>

    • 

  • 
#5
ect_check

    
                at gal-a11y-e-cell-text.c
                  line
                  69

    

    • 

  • 
#6
ect_get_name

    
                at gal-a11y-e-cell-text.c
                  line
                  81

    

    • 

  • 
#7
atk_object_get_name

    
                from
                /usr/lib/libatk-1.0.so.0

    

    • 

  • 
#8
gnome_accessibility_module_shutdown

    
                from
                /usr/lib/gtk-2.0/modules/libatk-bridge.so

    

    • 

  • 
#9
gnome_accessibility_module_shutdown

    
                from
                /usr/lib/gtk-2.0/modules/libatk-bridge.so

    

    • 

  • 
#10
g_signal_override_class_closure

    
                from
                /lib/libgobject-2.0.so.0

    

    • 

  • 
#11
g_signal_emit_valist

    
                from
                /lib/libgobject-2.0.so.0

    

    • 

  • 
#12
g_signal_emit

    
                from
                /lib/libgobject-2.0.so.0

    

    • 

  • 
#13
atk_object_notify_state_change

    
                from
                /usr/lib/libatk-1.0.so.0

    

    • 

  • 
#14
gal_a11y_e_cell_remove_state

    
                at gal-a11y-e-cell.c
                  line
                  525

    

    • 

  • 
#15
ectr_model_row_changed_cb

    
                at gal-a11y-e-cell-tree.c
                  line
                  48

    

    • 

  • 
#16
g_cclosure_marshal_VOID

    
                from
                /lib/libgobject-2.0.so.0

    

    • 

  • 
#17
g_closure_invoke

    
                from
                /lib/libgobject-2.0.so.0

    

    • 

  • 
#18
g_signal_override_class_closure

    
                from
                /lib/libgobject-2.0.so.0

    

    • 

  • 
#19
g_signal_emit_valist

    
                from
                /lib/libgobject-2.0.so.0

    

    • 

  • 
#20
g_signal_emit

    
                from
                /lib/libgobject-2.0.so.0

    

    • 

  • 
#21
e_table_model_row_changed

    
                at e-table-model.c
                  line
                  487

    

    • 

  • 
#22
e_tree_table_adapter_node_set_expanded

    
                at e-tree-table-adapter.c
                  line
                  1117

    

    • 

  • 
#23
e_tree_table_adapter_load_expanded_state

    
                at e-tree-table-adapter.c
                  line
                  1053

    

    • 

  • 
#24
e_tree_load_expanded_state

    
                at e-tree.c
                  line
                  2010

    

    • 

  • 
#25
regen_list_regened

    
                at message-list.c
                  line
                  1690

    

    • 

  • 
#26
mail_msgport_replied

    
                at mail-mt.c
                  line
                  461

    

    • 

  • 
#27
g_io_channel_unix_get_fd

    
                from
                /lib/libglib-2.0.so.0

    

    • 

  • 
#28
g_main_context_dispatch

    
                from
                /lib/libglib-2.0.so.0

    

    • 

  • 
#29
g_main_context_check

    
                from
                /lib/libglib-2.0.so.0

    

    • 

  • 
#30
g_main_loop_run

    
                from
                /lib/libglib-2.0.so.0

    

    • 

  • 
#31
bonobo_main

    
                from
                /usr/lib/libbonobo-2.so.0

    

    • 

  • 
#32
main

    
                at main.c
                  line
                  615

    

    • 

  • 
#33
__libc_start_main

    
                from
                /lib/libc.so.6

    

    • 

  • 
#34
_start

    • 

  • 
#0
__kernel_vsyscall

    • 













Comment 3


André Klapper





          2006-09-25 13:14:05 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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