Bug 1093322 - [abrt] evolution-data-server: g_thread_abort(): evolution-addressbook-factory killed by SIGABRT
Summary: [abrt] evolution-data-server: g_thread_abort(): evolution-addressbook-factory...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:6e2ebbc2a89208f0ecc6f2fc32e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-01 11:30 UTC by Laszlo Pal
Modified: 2014-06-11 07:14 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-11 07:14:49 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (38.82 KB, text/plain)
2014-05-01 11:30 UTC, Laszlo Pal 		no flags Details
File: cgroup (172 bytes, text/plain)
2014-05-01 11:30 UTC, Laszlo Pal 		no flags Details
File: core_backtrace (26.86 KB, text/plain)
2014-05-01 11:30 UTC, Laszlo Pal 		no flags Details
File: dso_list (15.93 KB, text/plain)
2014-05-01 11:31 UTC, Laszlo Pal 		no flags Details
File: environ (926 bytes, text/plain)
2014-05-01 11:31 UTC, Laszlo Pal 		no flags Details
File: limits (1.29 KB, text/plain)
2014-05-01 11:31 UTC, Laszlo Pal 		no flags Details
File: maps (75.54 KB, text/plain)
2014-05-01 11:31 UTC, Laszlo Pal 		no flags Details
File: open_fds (769 bytes, text/plain)
2014-05-01 11:31 UTC, Laszlo Pal 		no flags Details
File: proc_pid_status (959 bytes, text/plain)
2014-05-01 11:31 UTC, Laszlo Pal 		no flags Details
File: var_log_messages (222 bytes, text/plain)
2014-05-01 11:31 UTC, Laszlo Pal 		no flags Details
View All

Description Laszlo Pal 2014-05-01 11:30:48 UTC 
Version-Release number of selected component:
evolution-data-server-3.10.4-3.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-addressbook-factory
crash_function: g_thread_abort
executable:     /usr/libexec/evolution-addressbook-factory
kernel:         3.13.10-200.fc20.x86_64
runlevel:       unknown
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_thread_abort at gthread-posix.c:79
 #3 g_mutex_lock at gthread-posix.c:214
 #4 g_main_loop_quit at gmain.c:3932
 #5 source_registry_authenticate_respond_cb at e-source-registry.c:1777
 #9 g_main_context_iteration at gmain.c:3774
 #10 e_source_registry_authenticate_sync at e-source-registry.c:2119
 #11 book_backend_ldap_open at e-book-backend-ldap.c:5017
 #12 book_backend_open_thread_old_style at e-book-backend.c:965
 #13 book_backend_dispatch_thread at e-book-backend.c:187
 #14 io_job_thread at gioscheduler.c:89
Comment 1 Laszlo Pal 2014-05-01 11:30:53 UTC 
Created attachment 891451 [details]
File: backtrace
Comment 2 Laszlo Pal 2014-05-01 11:30:55 UTC 
Created attachment 891452 [details]
File: cgroup
Comment 3 Laszlo Pal 2014-05-01 11:30:57 UTC 
Created attachment 891453 [details]
File: core_backtrace
Comment 4 Laszlo Pal 2014-05-01 11:31:00 UTC 
Created attachment 891454 [details]
File: dso_list
Comment 5 Laszlo Pal 2014-05-01 11:31:02 UTC 
Created attachment 891455 [details]
File: environ
Comment 6 Laszlo Pal 2014-05-01 11:31:04 UTC 
Created attachment 891456 [details]
File: limits
Comment 7 Laszlo Pal 2014-05-01 11:31:07 UTC 
Created attachment 891457 [details]
File: maps
Comment 8 Laszlo Pal 2014-05-01 11:31:10 UTC 
Created attachment 891458 [details]
File: open_fds
Comment 9 Laszlo Pal 2014-05-01 11:31:12 UTC 
Created attachment 891459 [details]
File: proc_pid_status
Comment 10 Laszlo Pal 2014-05-01 11:31:14 UTC 
Created attachment 891460 [details]
File: var_log_messages
Comment 11 Milan Crha 2014-05-02 05:52:39 UTC 
Thanks for a bug report. I do not see from the backtrace what could cause the crash (I see where it crashed, but not why). A guess is that there happened some memory corruption, some code wrote to an already freed memory or something like that, which later caused this crash.

Do you have any steps what to do to reproduce this, please?
Comment 12 Laszlo Pal 2014-06-09 19:03:02 UTC 
Sorry for that but I can't provide the steps because it just happens time to time without notice. I don't really use Evolution it just for some calendar support, so for me it is not really dissapointing bug. If noone else reporting similar, I suggest to close it
Comment 13 Milan Crha 2014-06-11 07:14:49 UTC 
The problem with memory corruption issues is that they strike on various places, even though being caused by the same circumstances. As we do not have much clue, I agree with you and I'm closing this. For now.
Note You need to log in before you can comment on or make changes to this bug.