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 670046 - [abrt] evolution-3.2.3-1.fc16: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
[abrt] evolution-3.2.3-1.fc16: Process /usr/bin/evolution was killed by signa...
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
3.2.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-02-14 09:47 UTC by Milan Crha
Modified: 2015-03-10 16:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Crha 2012-02-14 09:47:27 UTC 
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=789046

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        evolution
executable:     /usr/bin/evolution
kernel:         3.2.2-1.fc16.i686
reason:         Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
time:           Wed 08 Feb 2012 11:20:40 AM CST

Core was generated by `evolution'.
Program terminated with signal 6, Aborted.

+ Trace 229656

Thread 7 (Thread 0xb77bab00 (LWP 23843))

  • #0 gtk_css_provider_get_style
    at gtkcssprovider.c line 1392
  • #1 gtk_style_provider_get_style
    at gtkstyleprovider.c line 83
  • #2 build_properties
    at gtkstylecontext.c line 927
  • #3 style_data_lookup
    at gtkstylecontext.c line 1034
  • #4 gtk_style_context_get_font
    at gtkstylecontext.c line 3461
  • #5 update_pango_context
    at gtkwidget.c line 9089
  • #6 gtk_widget_update_pango_context
    at gtkwidget.c line 9107
  • #7 gtk_widget_real_style_updated
    at gtkwidget.c line 6527
  • #8 gtk_label_style_updated
    at gtklabel.c line 3861
  • #9 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 85
  • #10 g_type_class_meta_marshal
    at gclosure.c line 885
  • #11 g_closure_invoke
    at gclosure.c line 774
  • #12 signal_emit_unlocked_R
    at gsignal.c line 3202
  • #13 g_signal_emit_valist
  • #14 g_signal_emit
    at gsignal.c line 3060
  • #15 style_context_changed
    at gtkwidget.c line 14503
  • #16 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 85
  • #17 g_closure_invoke
    at gclosure.c line 774
  • #18 signal_emit_unlocked_R
    at gsignal.c line 3272
  • #19 g_signal_emit_valist
  • #20 g_signal_emit
    at gsignal.c line 3060
  • #21 gtk_style_context_invalidate
    at gtkstylecontext.c line 3175
  • #22 gtk_style_context_set_path
    at gtkstylecontext.c line 1573
  • #23 gtk_widget_get_path
    at gtkwidget.c line 14489
  • #24 _gtk_widget_update_path
    at gtkwidget.c line 7734
  • #25 reset_style_recurse
    at gtkwidget.c line 8779
  • #26 gtk_box_forall
    at gtkbox.c line 1856
  • #27 gtk_container_forall
    at gtkcontainer.c line 2014
  • #28 reset_style_recurse
    at gtkwidget.c line 8782
  • #29 reset_style_recurse
    at gtkwidget.c line 8777
  • #30 gtk_frame_forall
    at gtkframe.c line 374
  • #31 gtk_container_forall
    at gtkcontainer.c line 2014
  • #32 reset_style_recurse
    at gtkwidget.c line 8782
  • #33 reset_style_recurse
    at gtkwidget.c line 8777
  • #34 gtk_widget_reset_style
    at gtkwidget.c line 8803
  • #35 gtk_box_forall
    at gtkbox.c line 1856
  • #36 gtk_container_foreach
    at gtkcontainer.c line 2041
  • #37 gtk_box_invalidate_order
    at gtkbox.c line 943
  • #38 gtk_box_pack
    at gtkbox.c line 991
  • #39 shell_taskbar_activity_add
    at e-shell-taskbar.c line 115
  • #40 g_cclosure_marshal_VOID__OBJECT
    at gmarshal.c line 644
  • #41 g_closure_invoke
    at gclosure.c line 774
  • #42 signal_emit_unlocked_R
    at gsignal.c line 3272
  • #43 g_signal_emit_valist
    at gsignal.c line 3003
  • #44 g_signal_emit
    at gsignal.c line 3060
  • #45 e_shell_backend_add_activity
    at e-shell-backend.c line 424
  • #46 mail_backend_job_started_cb
    at e-mail-backend.c line 602
  • #47 g_cclosure_marshal_VOID__OBJECT
    at gmarshal.c line 644
  • #48 g_closure_invoke
    at gclosure.c line 774
  • #49 signal_emit_unlocked_R
    at gsignal.c line 3272
  • #50 g_signal_emit_valist
    at gsignal.c line 3003
  • #51 g_signal_emit
    at gsignal.c line 3060
  • #52 session_start_job_cb
    at camel-session.c line 163
  • #53 g_idle_dispatch
    at gmain.c line 4801
  • #54 g_main_dispatch
    at gmain.c line 2441
  • #55 g_main_context_dispatch
    at gmain.c line 3011
  • #56 g_main_context_iterate
    at gmain.c line 3089
  • #57 g_main_loop_run
    at gmain.c line 3297
  • #58 gtk_main
    at gtkmain.c line 1362
  • #59 main
    at main.c line 709

Thread 2 (Thread 0xb75b8b40 (LWP 23844))

  • #0 __kernel_vsyscall
  • #1 read
    at ../sysdeps/unix/syscall-template.S line 82
  • #2 read
    at /usr/include/bits/unistd.h line 45
  • #3 unix_signal_helper_thread
    at gmain.c line 4567
  • #4 g_thread_create_proxy
    at gthread.c line 1962
  • #5 start_thread
    at pthread_create.c line 309
  • #6 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 133 






Comment 1


Milan Crha





          2012-02-14 09:51:20 UTC
        



Note the actual crash is this:
> *** glibc detected *** evolution: double free or
> corruption (!prev): 0x0aa8df58 ***

And it happens when entering a Trash folder, most likely. The question is whether this isn't caused by gtk+ itself, because I found couple similar crashed [1] involving gtk_css_provider_get_style() where is also reported memory corruption, though within different projects. As an example one from rhytmbox: bug #666066

[1] https://bugzilla.gnome.org/buglist.cgi?query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;bug_status=NEEDINFO;longdesc=gtk_css_provider_get_style;longdesc_type=allwordssubstr






Comment 2


Matthew Barnes





          2012-02-14 13:39:47 UTC
        



I've been seeing those crashes too for several weeks using the gtk-3-2 branch.  Haven't been able to catch it under valgrind yet.  Thought it might have been something in my branch but I guess not.






Comment 3


Milan Crha





          2012-02-14 16:55:32 UTC
        



Maybe it has something to do with bug #455900, which writes NULL to already freed memory, thus theoretically anywhere.






Comment 4


Milan Crha





          2012-04-11 06:57:21 UTC
        



Matthew, can this be caused by IMAP+, and the fixes you did before 3.4.0 release fixes this one too? I think of it after another similar bug report from 3.2.3:
https://bugzilla.redhat.com/show_bug.cgi?id=811372

> I deleted my google account in Gnome Online Accounts because I enabled two
> facto authentication in Google. Evolution asked for a new password
> (but the account no longer existed), enter the password and crash






Comment 5


Matthew Barnes





          2012-04-11 13:07:21 UTC
        



I didn't backport my "imapx" changes to 3.2 because they were too high risk.

During 3.3 I tried to make the backend more responsive to cancellations by giving the backend's Command and Job structs their own reference count and not waiting around for them to finish if the CamelOperation that spawned them gets cancelled.  That led to all manner of lifecycle issues since the backend wasn't designed for that, which led to all manner of followup fixes -- including during the code freeze.  I think that's what you're thinking of.






Comment 6


Milan Crha





          2015-03-10 16:48:59 UTC
        



No duplicate for a long time, I'm closing this.