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 629193 - evolution crashed with SIGSEGV in mail_msg_unref()
evolution crashed with SIGSEGV in mail_msg_unref()
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-09-09 16:52 UTC by Pedro Villavicencio
Modified: 2011-05-20 12:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32


Attachments
Backtrace with Pango symbols (39.06 KB, text/plain)
2010-09-09 20:14 UTC, Randy Barlow
Details

Description Pedro Villavicencio 2010-09-09 16:52:47 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/602928

"Evolution with MAPI plugin still crashes on start, when it process deleted message."

backtrace:

"Program received signal SIGSEGV, Segmentation fault.

Thread 1 (Thread 0x7ffff7fac940 (LWP 18062))

  • #0 g_slist_foreach
    at /build/buildd/glib2.0-2.25.15/glib/gslist.c line 851
  • #1 pango_layout_line_unref
    from /usr/lib/libpango-1.0.so.0
  • #2 ??
    from /usr/lib/libpango-1.0.so.0
  • #3 ??
    from /usr/lib/libpango-1.0.so.0
  • #4 g_object_unref
    at /build/buildd/glib2.0-2.25.15/gobject/gobject.c line 2580
  • #5 gtk_label_clear_layout
    at /build/buildd/gtk+2.0-2.21.7/gtk/gtklabel.c line 2909
  • #6 gtk_label_recalculate
    at /build/buildd/gtk+2.0-2.21.7/gtk/gtklabel.c line 1894
  • #7 IA__gtk_label_set_text
  • #8 activity_proxy_update
    at e-activity-proxy.c line 67
  • #9 g_closure_invoke
    at /build/buildd/glib2.0-2.25.15/gobject/gclosure.c line 766
  • #10 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.25.15/gobject/gsignal.c line 3252
  • #11 g_signal_emit_valist
    at /build/buildd/glib2.0-2.25.15/gobject/gsignal.c line 2983
  • #12 g_signal_emit
    at /build/buildd/glib2.0-2.25.15/gobject/gsignal.c line 3040
  • #13 g_object_dispatch_properties_changed
    at /build/buildd/glib2.0-2.25.15/gobject/gobject.c line 799
  • #14 g_object_notify_queue_thaw
    at /build/buildd/glib2.0-2.25.15/gobject/gobjectnotifyqueue.c line 132
  • #15 g_object_notify_by_spec_internal
    at /build/buildd/glib2.0-2.25.15/gobject/gobject.c line 857
  • #16 g_object_notify
    at /build/buildd/glib2.0-2.25.15/gobject/gobject.c line 898
  • #17 op_status_exec
    at mail-mt.c line 949
  • #18 mail_msg_idle_cb
    at mail-mt.c line 444
  • #19 g_main_dispatch
    at /build/buildd/glib2.0-2.25.15/glib/gmain.c line 2119
  • #20 g_main_context_dispatch
    at /build/buildd/glib2.0-2.25.15/glib/gmain.c line 2672
  • #21 g_main_context_iterate
    at /build/buildd/glib2.0-2.25.15/glib/gmain.c line 2750
  • #22 g_main_loop_run
    at /build/buildd/glib2.0-2.25.15/glib/gmain.c line 2958
  • #23 IA__gtk_main
    at /build/buildd/gtk+2.0-2.21.7/gtk/gtkmain.c line 1237
  • #24 main
    at main.c line 651

Comment 1 Matthew Barnes 2010-09-09 17:39:32 UTC
Looks to me like the crash is in Thread 1:

Thread 1 (Thread 0x7ffff7fac940 (LWP 18062))

  • #0 g_slist_foreach
    at /build/buildd/glib2.0-2.25.15/glib/gslist.c line 851
  • #1 pango_layout_line_unref
    from /usr/lib/libpango-1.0.so.0
  • #2 ??
    from /usr/lib/libpango-1.0.so.0
  • #3 ??
    from /usr/lib/libpango-1.0.so.0
  • #4 g_object_unref
    at /build/buildd/glib2.0-2.25.15/gobject/gobject.c line 2580

user_data=0x1 looks suspicious to me, but the trace is missing pango symbols so I can't really tell what's going on.

Thread 18 stopped at line 177 of mail-mt.c which, at least in versions 2.30.2 and 2.30.3 is just:

   g_return_if_fail (mail_msg->ref_count > 0);

and the trace shows that mail_msg was not NULL.  In fact we check for that in the line before.

Can you try to get another trace with Pango symbols so I can see if the user_data=0x1 is innocent or not?
Comment 2 Randy Barlow 2010-09-09 20:14:17 UTC
Created attachment 169891 [details]
Backtrace with Pango symbols

I installed the libpango1.0-0-dbgsym ubuntu package, and regenerated the backtrace information. Let me know if there is any further information that would be helpful!
Comment 3 Akhil Laddha 2010-10-22 03:56:56 UTC
Information provided.
Comment 4 Randy Barlow 2010-10-22 14:19:25 UTC
The latest versions of evolution (2.30.3-1ubuntu6) and evolution-mapi (0.30.3-1ubuntu1) in Ubuntu Maverick allow me to read my mail without this crash.
Comment 5 Akhil Laddha 2011-04-07 06:34:16 UTC
Can you please check again whether this issue still happens in Evolution 2.32.2 or 3.0 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.
Comment 6 Akhil Laddha 2011-05-20 12:06:32 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!