Bug 644120 – [abrt] evolution-2.32.1-1.fc14: malloc_consolidate: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)

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 644120 - [abrt] evolution-2.32.1-1.fc14: malloc_consolidate: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)


Summary:	[abrt] evolution-2.32.1-1.fc14: malloc_consolidate: Process /usr/bin/evolutio...


Status:	RESOLVED OBSOLETE

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.32.x (obsolete)
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-03-07 15:03 UTC by Milan Crha
Modified:	2012-09-04 19:01 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Milan Crha 2011-03-07 15:03:00 UTC

Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=682730

abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 61220 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 100962304 bytes
crash_function: malloc_consolidate
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.fc14.i686
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299498883
uid: 501

How to reproduce
-----
1.configure e-mail client
2.check e-mail
3.crash happened
Core was generated by `evolution'.
Program terminated with signal 11, Segmentation fault.

+ Trace 226216

Thread 1 (Thread 0xb77da880 (LWP 2757))

#0 malloc_consolidate
at malloc.c line 5155
#1 _int_malloc
at malloc.c line 4373
#2 __libc_malloc
at malloc.c line 3660
#3 g_realloc
at gmem.c line 233
#4 g_string_maybe_expand
at gstring.c line 396
#5 g_string_sized_new
at gstring.c line 421
#6 activity_describe
at e-activity.c line 220
#7 e_activity_describe
at e-activity.c line 448
#8 activity_proxy_update
at e-activity-proxy.c line 67
#9 g_cclosure_marshal_VOID__PARAM
at gmarshal.c line 533
#10 g_closure_invoke
at gclosure.c line 766
#11 signal_emit_unlocked_R
at gsignal.c line 3252
#12 g_signal_emit_valist
at gsignal.c line 2983
#13 g_signal_emit
at gsignal.c line 3040
#14 g_object_dispatch_properties_changed
at gobject.c line 914
#15 g_object_notify_dispatcher
at gobject.c line 324
#16 g_object_notify_queue_thaw
at gobjectnotifyqueue.c line 132
#17 g_object_notify_by_spec_internal
at gobject.c line 972
#18 g_object_notify
at gobject.c line 1013
#19 e_activity_set_primary_text
at e-activity.c line 561
#20 op_status_exec
at mail-mt.c line 947
#21 mail_msg_idle_cb
at mail-mt.c line 442
#22 g_idle_dispatch
at gmain.c line 4254
#23 g_main_dispatch
at gmain.c line 2149
#24 g_main_context_dispatch
at gmain.c line 2702
#25 g_main_context_iterate
at gmain.c line 2780
#26 g_main_loop_run
at gmain.c line 2988
#27 IA__gtk_main
at gtkmain.c line 1237
#28 main
at main.c line 679

Comment 1 Milan Crha 2012-09-04 19:01:07 UTC

Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.