Bug 712572 – [abrt] Possible race condition in SMTP provider

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 712572 - [abrt] Possible race condition in SMTP provider


Summary:	[abrt] Possible race condition in SMTP provider


Status:	RESOLVED INCOMPLETE

Product:	evolution-data-server
Classification:	Platform
Component:	Mailer
Version:	3.8.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:	2013-11-18 10:49 UTC by Milan Crha
Modified:	2014-11-28 09:42 UTC

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

Description Milan Crha 2013-11-18 10:49:22 UTC

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

Description of problem:
I had prepared a number of messages that were to be signed and encrypted. Each message had one attachment. Then I started sending them. I didn't wait for each one to be sent before I gave the send command on the next one, so at times there were two messages being sent at once. Then all of a sudden Evolution crashed.

Version-Release number of selected component:
evolution-3.8.5-2.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        evolution
crash_function: ssl_DestroyLocks
executable:     /usr/bin/evolution
kernel:         3.11.6-201.fc19.x86_64


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

+ Trace 232789

Thread 1 (Thread 0x7fbb73dfb700 (LWP 13293))

#0 __GI_raise
at ../nptl/sysdeps/unix/sysv/linux/raise.c line 56
#1 __GI_abort
at abort.c line 90
#2 __libc_message
at ../sysdeps/unix/sysv/linux/libc_fatal.c line 196
#3 malloc_printerr
at malloc.c line 4937
#4 _int_free
at malloc.c line 3936
#5 ssl_DestroyLocks
at sslsock.c line 308
#6 ssl_FreeSocket
at sslsock.c line 407
#7 ssl_DefClose
at ssldef.c line 205
#8 tcp_stream_raw_finalize
at camel-tcp-stream-raw.c line 185
#9 g_object_unref
from /lib64/libgobject-2.0.so.0
#10 smtp_transport_disconnect_sync
at camel-smtp-transport.c line 468
#11 service_disconnect_thread
at camel-service.c line 834
#12 run_in_thread
from /lib64/libgio-2.0.so.0
#13 io_job_thread
from /lib64/libgio-2.0.so.0
#14 g_task_thread_pool_thread
from /lib64/libgio-2.0.so.0
#15 g_thread_pool_thread_proxy
from /lib64/libglib-2.0.so.0
#16 g_thread_proxy
from /lib64/libglib-2.0.so.0
#17 start_thread
at pthread_create.c line 308
#18 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 113

Comment 1 Milan Crha 2013-11-18 10:51:09 UTC

I know this is 3.8.5 and 3.11.x moved away from direct NSS usage, but still, there can be an issue with concurrent usage of a CamelService, in this case SMTP.

Comment 2 Milan Crha 2014-11-28 09:42:42 UTC

I might be wrong with the above comment.