Bug 663084 – [abrt] evolution-data-server-3.2.1-1.fc16: io_error: Process /usr/libexec/e-addressbook-factory 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 663084 - [abrt] evolution-data-server-3.2.1-1.fc16: io_error: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)


Summary:	[abrt] evolution-data-server-3.2.1-1.fc16: io_error: Process /usr/libexec/e-a...


Status:	RESOLVED FIXED

Product:	libsoup
Classification:	Core
Component:	HTTP Transport
Version:	2.36.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	libsoup-maint@gnome.bugs
QA Contact:	libsoup-maint@gnome.bugs

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-10-31 08:02 UTC by Milan Crha
Modified:	2012-07-19 13:07 UTC

See Also:
GNOME target:	---
GNOME version:	3.1/3.2

Description Milan Crha 2011-10-31 08:02:55 UTC

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

libreport version: 2.0.6
abrt_version:   2.0.4.981
backtrace_rating: 4
cmdline:        /usr/libexec/e-addressbook-factory
comment:        I don't know.
crash_function: io_error
executable:     /usr/libexec/e-addressbook-factory
kernel:         3.1.0-1.fc16.x86_64
reason:         Process /usr/libexec/e-addressbook-factory was killed by signal
11 (SIGSEGV)
time:           Sun Oct 30 04:15:18 2011

Core was generated by `/usr/libexec/e-addressbook-factory'.
Program terminated with signal 11, Segmentation fault.

+ Trace 228950

Thread 7 (Thread 0x7f7fed697700 (LWP 2034))

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

Thread 2 (Thread 0x7f7ff23577c0 (LWP 2011))

#0 _g_dbus_debug_emission
at gdbusprivate.c line 1775
#1 g_dbus_connection_emit_signal
at gdbusconnection.c line 4895
#2 e_gdbus_signal_emission_hook_strv
at e-gdbus-templates.c line 163
#3 signal_emit_unlocked_R
at gsignal.c line 3238
#4 g_signal_emit_valist
at gsignal.c line 3003
#5 g_signal_emit
at gsignal.c line 3060
#6 e_data_book_view_notify_complete
at e-data-book-view.c line 564
#7 finish_operation
at e-book-backend-google.c line 558
#8 check_get_new_contacts_finished
at e-book-backend-google.c line 609
#9 check_get_new_contacts_finished
at e-book-backend-google.c line 596
#10 get_new_contacts_cb
at e-book-backend-google.c line 810
#11 g_simple_async_result_complete
at gsimpleasyncresult.c line 749
#12 complete_in_idle_cb_for_thread
at gsimpleasyncresult.c line 817
#13 g_main_dispatch
at gmain.c line 2425
#14 g_main_context_dispatch
at gmain.c line 2995
#15 g_main_context_iterate
at gmain.c line 3073
#16 g_main_loop_run
at gmain.c line 3281
#17 main
at e-data-book-factory.c line 892

Thread 1 (Thread 0x7f7fdde9f700 (LWP 23411))

#0 io_error
at soup-message-io.c line 180
#1 read_metadata
at soup-message-io.c line 310
#2 io_read
at soup-message-io.c line 846
#3 g_closure_invoke
at gclosure.c line 774
#4 signal_emit_unlocked_R
at gsignal.c line 3272
#5 g_signal_emit_valist
at gsignal.c line 3003
#6 g_signal_emit
at gsignal.c line 3060
#7 soup_socket_disconnect
at soup-socket.c line 1126
#8 soup_connection_disconnect
at soup-connection.c line 706
#9 clear_current_item
at soup-connection.c line 426
#10 soup_connection_set_state
at soup-connection.c line 784
#11 soup_session_unqueue_item
at soup-session.c line 1502
#12 process_queue_item
at soup-session-sync.c line 310
#13 send_message
at soup-session-sync.c line 378
#14 _gdata_service_actually_send_message
at gdata/gdata-service.c line 618
#15 _gdata_service_send_message
at gdata/gdata-service.c line 667
#16 _gdata_service_query
at gdata/gdata-service.c line 880
#17 __gdata_service_query
at gdata/gdata-service.c line 908
#18 query_thread
at gdata/gdata-service.c line 757
#19 run_in_thread
at gsimpleasyncresult.c line 843
#20 io_job_thread
at gioscheduler.c line 180
#21 g_thread_pool_thread_proxy
at gthreadpool.c line 319
#22 g_thread_create_proxy
at gthread.c line 1962
#23 start_thread
at pthread_create.c line 309
#24 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115

Comment 1 Reinout van Schouwen 2011-11-04 15:48:18 UTC

This occurred to me as well.

Comment 2 Reinout van Schouwen 2012-05-11 14:23:47 UTC

Dear Evolution developers, even though you don't see it because ABRT goes to RedHat bugzilla, I'm having this crash on an almost daily basis. Could anyone care to take a look at it, please?

Comment 3 Milan Crha 2012-05-14 11:45:21 UTC

The crash happens below libgdata, which doesn't necessary mean that it's not evolution's fault, but it would be better to ask there first.

Philip, did you see anything similar in 3.2.x+, please?

Comment 4 Philip Withnall 2012-05-14 22:56:33 UTC

Could this be bug #637741? What version of libsoup was being used?

Comment 5 Reinout van Schouwen 2012-06-11 22:12:28 UTC

(In reply to comment #4)
> Could this be bug #637741? What version of libsoup was being used?

The one bundled with Fedora 16, which would be 2.36.1.

Comment 6 Philip Withnall 2012-06-17 19:28:52 UTC

(In reply to comment #5)
> (In reply to comment #4)
> > Could this be bug #637741? What version of libsoup was being used?
> 
> The one bundled with Fedora 16, which would be 2.36.1.

Probably not bug #637741 then, although it looks similar.

I can’t see what in libgdata/EDS is causing this, and suspect it might be a libsoup problem.

It looks like the SoupMessage in thread 1 (0x7f7fe000e2e0) is getting destroyed between entering read_metadata(), since http://git.gnome.org/browse/libsoup/tree/libsoup/soup-message-io.c?id=LIBSOUP_2_36_1#n272 succeeds, and SOUP_SOCKET_ERROR being handled, since http://git.gnome.org/browse/libsoup/tree/libsoup/soup-message-io.c?id=LIBSOUP_2_36_1#n179 fails.

I don’t know enough about the SoupMessage lifecycle in libsoup to work out what could be destroying it. libgdata certainly holds a reference to the SoupMessage while sending it: http://git.gnome.org/browse/libgdata/tree/gdata/gdata-service.c?id=LIBGDATA_0_10_1#n618.

Comment 7 Milan Crha 2012-06-20 17:05:12 UTC

Similar downstream  bug report from 3.4.2:
https://bugzilla.redhat.com/show_bug.cgi?id=833459

Comment 8 Dan Winship 2012-07-11 13:32:27 UTC

The refcount of the message should be at least 3 at that point... there's no way it could be getting destroyed.

Is there any stderr / .xsession-errors associated with the crash?

Comment 9 Reinout van Schouwen 2012-07-11 21:54:12 UTC

(In reply to comment #8)

> Is there any stderr / .xsession-errors associated with the crash?

Have you checked the downstream RH bug and duplicates? There's quite some ABRT info there.

Comment 10 Dan Winship 2012-07-12 12:48:54 UTC

There's lots of abrt info, but no .xsession-errors, which is the thing (other than the backtrace) that would be most useful here.

Comment 11 Milan Crha 2012-07-13 13:24:36 UTC

I just got similar downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=839614

It also contains .xsession_errors, though nothing interesting at the end of it.

Dan, would you mind to look at it and write your thoughts there, please?

Comment 12 Dan Winship 2012-07-19 13:07:22 UTC

This bug no longer exists in git master. I've fixed it on the gnome-3-4 branch (http://git.gnome.org/browse/libsoup/commit/?h=gnome-3-4&id=ae6bc194), and I'm building new f17 packages now.