I confirm too the bad behaviour with Google account. Worked around deactivating
calendar sync.
This is a problem, anyway.
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Indicator Date and Time.
https://bugs.launchpad.net/bugs/774071
I confirm the bad behavior on my side with google account enabled..
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Indicator Date and Time.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
The problem seems to be that one call to
e_cal_client_get_objects_for_uid does not result in a callback when
querying a uid with infinite entries. Probably ecal tries to fetch all
of them?
Is there a different ecal function that one could call? How is it done
in Evolution or Gnome calendar, so
Output generated with:
valgrind --tool=massif
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
Can be viewed with:
ms_print massif.out.8535 | less
Might be the following function be at fault?
unity::indicator::datetime::EdsEngine::Impl::fetch_detached_instances(_GObject*,
This is still an issue in Ubuntu 20.04.
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Indicator Date and Time.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
Status in Indicator Date
No. I see it in 17.10 as of today (2018-01-09). I cannot log intro Unity
because of this bug. Right after login, indicator-datetime-service" eats
all of my CPU, breaks, starts again, eats all of my CPU, breaks, starts
again, eats all of my CPU, breaks, starts again, eats all of my CPU,
breaks,
The problem went away in 17.10. Cheers.
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Indicator Date and Time.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
Status in Indicator Date
Last work-around didn't stick. Don't think this bug or #1731939 is about
indicator-datetime-service. It seems to be evolution calendar that is
the problem. See comment below:
https://bugs.launchpad.net/ubuntu/+source/indicator-
datetime/+bug/1731939/comments/4
Will test 17.10 now.
--
You
(#51 was a mistake)
Sorry, wrote incorrect. Reported for 17.04 LTS above.
Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the "Show
a clock in the menu bar" in System Settings for Time & Date. Worked
after cold reboot.
--
You received this bug notification because you are a
Sorry, wrote incorrect. Reported for 17.04 LTS above.
Work-around (I cant upgrade to 17.10 due to KVM bug): Turn of the t
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Indicator Date and Time.
https://bugs.launchpad.net/bugs/774071
Seeing this on 17.10 as well. Battery indicator says ("estimating,
100%) and indicator-datetime-service uses between 2.4 GiB and (mostly)
~14.5 GiB RAM. CPU usage stays at 25% all the time. The indicator-
datetime-service crashes after reaching all available RAM, then restarts
with new PID.
I
Seeing this after upgrade from 16.04 to 16.10
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Indicator Date and Time.
https://bugs.launchpad.net/bugs/774071
Title:
Indicator-datetime-service renders 100% CPU usage
Status in Indicator
Since I upgraded to 12.04 recently I've started to notice this problem.
Namely, indicator-datetime-service was still running at 100% CPU, and
was quickly restarted (with just highter PID) after killing its process.
However, I was puzzled why at the same time some geoclue- related
service also
13 matches
Mail list logo
