Bug 1328846

Summary: [abrt] evolution-data-server: g_malloc(): evolution-calendar-factory-subprocess killed by SIGABRT
Product: [Fedora] Fedora Reporter: deadrat <jayabharat>
Component: evolution-data-serverAssignee: Milan Crha <mcrha>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7e33a5f787530f9dc04e7af4bf84b7d899561ad6
Whiteboard: abrt_hash:a15cbcb71fc9207e01ccf1ec3b2a6c09d3be744b;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 20:03:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description deadrat 2016-04-20 12:13:37 UTC 
Description of problem:
everytime I login, I see many processes regd "evolution-calendar-factory" taking up RAM. 

I tried killing it. 

It happened. 


P.S. : I don't want that process. I do not even have evolution installed anymore. I had already uninstalled it. 

Version-Release number of selected component:
evolution-data-server-3.18.5-1.fc23

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-calendar-factory-subprocess --factory local --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx6296x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/6296/2
crash_function: g_malloc
executable:     /usr/libexec/evolution-calendar-factory-subprocess
global_pid:     6312
kernel:         4.4.6-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #6 g_malloc at gmem.c:94
 #7 g_memdup at gstrfuncs.c:391
 #8 g_bytes_new at gbytes.c:96
 #9 g_variant_new_from_trusted at gvariant.c:294
 #10 g_variant_new_byte at gvariant.c:384
 #11 g_variant_valist_new_leaf at gvariant.c:4857
 #12 g_variant_valist_new at gvariant.c:5031
 #14 g_variant_new_va at gvariant.c:5259
 #15 g_variant_builder_add at gvariant.c:5415
 #16 g_dbus_message_to_blob at gdbusmessage.c:2668
Comment 1 deadrat 2016-04-20 12:13:45 UTC 
Created attachment 1149054 [details]
File: backtrace
Comment 2 deadrat 2016-04-20 12:13:46 UTC 
Created attachment 1149055 [details]
File: cgroup
Comment 3 deadrat 2016-04-20 12:13:49 UTC 
Created attachment 1149056 [details]
File: core_backtrace
Comment 4 deadrat 2016-04-20 12:13:51 UTC 
Created attachment 1149057 [details]
File: dso_list
Comment 5 deadrat 2016-04-20 12:13:53 UTC 
Created attachment 1149059 [details]
File: environ
Comment 6 deadrat 2016-04-20 12:13:55 UTC 
Created attachment 1149060 [details]
File: limits
Comment 7 deadrat 2016-04-20 12:13:57 UTC 
Created attachment 1149061 [details]
File: maps
Comment 8 deadrat 2016-04-20 12:13:59 UTC 
Created attachment 1149062 [details]
File: mountinfo
Comment 9 deadrat 2016-04-20 12:14:01 UTC 
Created attachment 1149063 [details]
File: namespaces
Comment 10 deadrat 2016-04-20 12:14:03 UTC 
Created attachment 1149064 [details]
File: open_fds
Comment 11 deadrat 2016-04-20 12:14:05 UTC 
Created attachment 1149065 [details]
File: proc_pid_status
Comment 12 deadrat 2016-04-20 12:14:06 UTC 
Created attachment 1149066 [details]
File: var_log_messages
Comment 13 Milan Crha 2016-04-25 12:24:49 UTC 
Thanks for a bug report. The evolution is only one of the clients of the evolution-data-server. Another one is gnome-shell itself, when it provides you with your events in the clock applet. The backend shows some issue in the local calendar (or task list or memo list).

Could you check what is stored in
   ~/.local/share/evolution/calendar
   ~/.local/share/evolution/memos
   ~/.local/share/evolution/tasks

There should be your events, tasks and memos you entered in the On This Computer calendars/task lists/memo lists. I would also check Online Accounts in the Settings, and disable any Calendar components if you do not want to use that feature (supposing you have any Online Accounts configured; if you do not, then you are safe).

Please do not delete those files/folders in ~/.local/share/evolution, they might be good for test purpose, to be able to reproduce the crash/CPU usage. Only move them away, thus the calendars/... will start with an empty content.
Comment 14 deadrat 2016-07-05 08:51:28 UTC 
(In reply to Milan Crha from comment #13)
Hi, 

Thanks for looking into this. 
I haven't added any items locally; but I do have online accounts added which could sync the Calendar. 
I have disabled the Calendar sync in those accounts. I haven't faced any crash yet. 

But there are still four or five "evolution-calendar-factory-subprocess" running all the time, collectively taking up approx 100 MB. 

[ I have also upgraded my OS now. I use rawhide. I do not use evolution (or any email client) anymore. ]
Comment 15 Milan Crha 2016-07-07 09:44:29 UTC 
Do you have evolution installed? If you do, then it autostarts
evolution-alarm-notify process on the session login, which opens the calendars. Your desktop environment can also request available calendars, for example GNOME shell does. As the evolution-calendar-factory-subprocess-s go from the evolution-data-server, then any application (client) can connect to them.

By the way, the first argument of the subprocess is --factory, it claims what calendars are served by the subprocess.

I'm not sure, should I close this for now and we'll wait if this will arise again?
Comment 16 Fedora End Of Life 2016-11-25 07:24:52 UTC 
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 17 Fedora End Of Life 2016-12-20 20:03:16 UTC 
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.