Description of problem:
evolution-2.28.3-10.el6: g_slice_alloc: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Evolution is getting crash.
It should not crash.
Backtrace, coredump attached.
Created attachment 463719 [details]
Created attachment 463721 [details]
Created attachment 463723 [details]
Thanks for a bug report. This is crashing somewhere in pango, which might mean either bug in there or some memory corruption caused by Evolution or other library it is using.
Main question is whether you are able to reproduce this. Are you? Because if so, then I would try to run evolution under valgrind and see what it'll show, because it may uncover that memory corruption. I would run valgrind like this:
$ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>evo.log
Evolution will be very slow, due to all memory checking, but it may show results at the end. Please give this a try and report back. Thanks in advance.
Thread 1 (Thread 4483):
#0 magazine_chain_pop_head (mem_size=16) at gslice.c:474
chunk = 0x1
#1 thread_memory_magazine1_alloc (mem_size=16) at gslice.c:777
#2 IA__g_slice_alloc (mem_size=16) at gslice.c:815
#3 0x0000003cf2457df6 in IA__g_slist_append (list=0x0, data=0x24fb610) at gslist.c:117
#4 0x0000003cfb42027f in reorder_runs_recurse (items=<value optimized out>, n_items=1) at pango-layout.c:4758
#5 0x0000003cfb421dd7 in pango_layout_line_reorder (layout=0x2584f10) at pango-layout.c:4786
#6 pango_layout_line_postprocess (layout=0x2584f10) at pango-layout.c:5186
#7 process_line (layout=0x2584f10) at pango-layout.c:3587
#8 pango_layout_check_lines (layout=0x2584f10) at pango-layout.c:3850
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.