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 594543 - Crash on folder/message change
Crash on folder/message change
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 595811 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-09-08 20:05 UTC by David Ronis
Modified: 2013-09-13 01:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Attachments
proposed evo patch (1.39 KB, patch)
2009-09-23 14:04 UTC, Milan Crha
committed Details | Review

Description David Ronis 2009-09-08 20:05:52 UTC
Version: 2.30.x

What were you doing when the application crashed?
I'd just switched to a folder that had one (new) email.  The e-mail's line in the summary blinked off and then on.   Afterwards, the bug-buddy poped up.  I've reported this before 


Distribution: Slackware Slackware 12.2.0
Gnome Release: 2.27.91 2009-08-25 (GARNOME)
BugBuddy Version: 2.27.92

System: Linux 2.6.30.5 #42 SMP PREEMPT Mon Aug 17 17:30:13 EDT 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10699900
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad

Memory status: size: 276410368 vsize: 276410368 resident: 72585216 share: 26218496 rss: 72585216 rss_rlim: 18446744073709551615
CPU usage: start_time: 1252437601 rtime: 6998 utime: 6156 stime: 842 cutime:63 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/garnome-svn-2.27/bin/evolution'

[Thread debugging using libthread_db enabled]
[New Thread 0xb5e4e710 (LWP 11622)]
[New Thread 0xa958eb90 (LWP 24354)]
[New Thread 0xafcf3b90 (LWP 11863)]
[New Thread 0xb0535b90 (LWP 11862)]
[New Thread 0xb0eb3b90 (LWP 11703)]
[New Thread 0xb16b3b90 (LWP 11702)]
0xb6112171 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0xb5e4e710 (LWP 11622))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at gspawn.c line 386
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 700
  • #3 run_bug_buddy
    at gnome-breakpad.cc line 369
  • #4 bugbuddy_segv_handle
    at gnome-breakpad.cc line 440
  • #5 <signal handler called>
  • #6 IA__g_object_unref
    at gobject.c line 2370
  • #7 tree_state_changed
    at gal-view-etable.c line 261
  • #8 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #9 IA__g_closure_invoke
    at gclosure.c line 767
  • #10 signal_emit_unlocked_R
    at gsignal.c line 3247
  • #11 IA__g_signal_emit_valist
    at gsignal.c line 2980
  • #12 IA__g_signal_emit
    at gsignal.c line 3037
  • #13 e_tree_state_change
    at e-tree.c line 294
  • #14 gal_view_etable_attach_tree
    at gal-view-etable.c line 288
  • #15 mail_shell_content_display_view_cb
    at e-mail-shell-content.c line 274
  • #16 e_mail_shell_content_update_view_instance
    at e-mail-shell-content.c line 1026
  • #17 mail_shell_view_reader_changed_cb
    at e-mail-shell-view-private.c line 173
  • #18 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #19 IA__g_closure_invoke
    at gclosure.c line 767
  • #20 signal_emit_unlocked_R
    at gsignal.c line 3247
  • #21 IA__g_signal_emit_valist
    at gsignal.c line 2980
  • #22 IA__g_signal_emit
    at gsignal.c line 3037
  • #23 mail_reader_emit_folder_loaded
    at e-mail-reader.c line 1846
  • #24 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #25 IA__g_closure_invoke
    at gclosure.c line 767
  • #26 signal_emit_unlocked_R
    at gsignal.c line 3247
  • #27 IA__g_signal_emit_valist
    at gsignal.c line 2980
  • #28 IA__g_signal_emit
    at gsignal.c line 3037
  • #29 main_folder_changed
    at message-list.c line 3405
  • #30 do_async_event
    at mail-mt.c line 681
  • #31 idle_async_event
    at mail-mt.c line 692
  • #32 g_idle_dispatch
    at gmain.c line 4065
  • #33 IA__g_main_context_dispatch
    at gmain.c line 1960
  • #34 g_main_context_iterate
    at gmain.c line 2591
  • #35 IA__g_main_loop_run
    at gmain.c line 2799
  • #36 IA__gtk_main
    at gtkmain.c line 1205
  • #37 main
    at main.c line 598
  • #0 waitpid
    from /lib/libpthread.so.0


---- Critical and fatal warnings logged during execution ----

** Gdk **: gdk_draw_layout: assertion `GDK_IS_GC (gc)' failed 
** Gdk **: gdk_gc_set_clip_rectangle: assertion `GDK_IS_GC (gc)' failed 
** Gdk **: gdk_gc_set_foreground: assertion `GDK_IS_GC (gc)' failed 
** Gdk **: gdk_gc_set_clip_rectangle: assertion `GDK_IS_GC (gc)' failed 
** Gdk **: gdk_draw_layout: assertion `GDK_IS_GC (gc)' failed 
** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed 
** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed 
** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed 
** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed 
** Gdk **: gdk_cursor_unref: assertion `cursor != NULL' failed 
** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed 
** Gdk **: gdk_cursor_unref: assertion `cursor != NULL' failed 
** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed 
** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed 
** Gdk **: gdk_cursor_unref: assertion `cursor != NULL' failed
Comment 1 Akhil Laddha 2009-09-09 04:38:18 UTC
David, could you please make sure that you file bug against correct evolution version. 

looks like crash in gal
Comment 2 David Ronis 2009-09-09 15:13:34 UTC
Hi Akhil,

I'll try, but I get confused with what version the git master really is.   More to the point, I've had my MAPI account disabled for several weeks, and the GAL has never worked for me in MAPI.   The crash happened several times yesterday (and the GAL is definitely off).   One other observation:  it only seems to happen in folders with 1 message.  My big folders seem to be immune.
Comment 3 David Ronis 2009-09-09 15:42:41 UTC
oops.  I spoke too quickly.  I just had a crash in a (local) folder where there were 2 new e-mails, and nothing else.  I had looked at the 1st and then then crtl-a'd and deleted them both.
Comment 4 David Ronis 2009-09-16 19:24:44 UTC
I just had this happen in a folder that contained 38 unread messages (and no others);  I'd selected the 1st one to read; they all blinked off and on and I crashed when switching folders.
Comment 5 Milan Crha 2009-09-22 08:48:45 UTC
*** Bug 595811 has been marked as a duplicate of this bug. ***
Comment 6 Milan Crha 2009-09-22 08:49:57 UTC
I got very similar crash as in bug #595811, which I believe is same as this one. I'm trying to reproduce and hunt it.
Comment 7 Milan Crha 2009-09-23 14:04:11 UTC
Created attachment 143794 [details] [review]
proposed evo patch

for evolution;

This change seems to do the trick. First of all, there is no need to create a GalView again and again on a reader change, as it was recreated on each message change. It leaded to some reference counting "errors" on the ETreee "tree" parameter of a gal_view_etable_attach_tree (the ref_count had been increased to 2 and 3). After this change the ref_count is always 1, which I believe is correct.
Comment 8 Milan Crha 2009-09-23 14:07:47 UTC
I forgot to add: it'll be great if anyone can give a try to the patch.

My steps are as follows:
a) Local Inbox with two messages, none selected
b) remote folder with one message selected
c) close evolution in folder from b)
d) open evolution, it'll be in folder from b), message selected and shown
   in a preview
e) switch to folder from a), no message selected, preview is empty
f) select first message, evolution crashes quite often
Comment 9 Matthew Barnes 2009-09-23 15:35:19 UTC
I get this crash all the time when cleaning out my Junk folder with one message.  Patch looks promising... I'll give it a test drive.
Comment 10 David Ronis 2009-09-23 22:20:53 UTC
I applied the patch and rebuilt the git/master (as well as all of gnome 2.28.0--ouch).  So far I haven't been able to get evolution to crash.
Comment 11 Matthew Barnes 2009-09-23 22:24:08 UTC
Committed a slightly more compact version of Milan's patch, but it does the same thing.  I haven't been able to reproduce the crash either with the path.  Let's assume it's fixed and reopen if one of us sees it again.
Comment 12 Matthew Barnes 2009-09-23 22:24:49 UTC
Whoops, forgot the commit link.

http://git.gnome.org/cgit/evolution/commit/?id=0c1afa3941ef2663793d0b5e1fd9221423374d19