[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

2021-08-16 Thread Jeff Silverman
ai_ja_nai (albertomassidda), while it is true that the bug is still
alive and kicking, there is a way to work around the issue.  See bug
1652789,  https://bugs.launchpad.net/ubuntu/+source/indicator-
datetime/+bug/1652789/comments/4 .
https://askubuntu.com/questions/876524/how-do-i-begin-to-diagnose-and-
fix-indicator-datetime-service-using-100-cpu-and#1022408 describes, in a
fairly detailed way, how to disable the local calendar from the online
calendar.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1642634

Title:
  indicator-datetime uses excessive memory

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

2021-04-07 Thread ai_ja_nai
Confirm that this bug is still alive and kicking on Ubuntu 20.04.
This effectively prevents using Ubuntu as a business OS...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1642634

Title:
  indicator-datetime uses excessive memory

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

2020-02-05 Thread Crimbo
@rael-gc is experiencing this issue still with 18.04 on duplicate bug post...
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1652789

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1642634

Title:
  indicator-datetime uses excessive memory

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

2017-11-16 Thread machadoug
Still having this issue with Ubuntu 17.10.
Disabled the option to Show clock in the menu bar and it still causes the issue.
Iǜe also set the time manually instead of Automatically from the internet and 
it has no effect.
Does anyone have a workaround?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1642634

Title:
  indicator-datetime uses excessive memory

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

2017-01-27 Thread Rodney Dawes
** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1642634

Title:
  indicator-datetime uses excessive memory

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

2017-01-02 Thread Crimbo
Scrap that... I realised it was because I had the 'indicator-datetime-
service' package set to 'stop' in the system monitor (which is a great
temporary fix if anyone is having this same issue).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1642634

Title:
  indicator-datetime uses excessive memory

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

2017-01-02 Thread Crimbo
This seems to have been resolved now, since running a system update on
Yakkety via 'Ubuntu Software'. Can anyone else confirm the same?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1642634

Title:
  indicator-datetime uses excessive memory

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

2016-11-21 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: None => x1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1642634

Title:
  indicator-datetime uses excessive memory

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

2016-11-21 Thread Pat McGowan
** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1642634

Title:
  indicator-datetime uses excessive memory

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory

2016-11-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1642634

Title:
  indicator-datetime uses excessive memory

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  On my Aquaris 4.5, OTA-13, indicator-datetime
  15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS
  is 315892, almost three times as much as unity8.

  I believe this is an OTA regression. I'm not sure if it regressed from
  OTA-11 or OTA-12.

  Just now, I got caught in an oom killer loop with constant killing of
  unity8-dash because of this, making my phone unusable. I had to kill
  indicator-datetime manually. It then restarted automatically and now
  uses 80456 RSS only. I see bug 1633319 exists complaining about a
  memory leak. It's not exactly the same version since mine is
  15.10+15.04.20160820.1-0ubuntu1 and that one is
  15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are
  the same or something? Perhaps the two are dupes, but I'll let someone
  more familiar make that determination.

  I have only a handful of alarms (perhaps five on average; rarely more)
  but I do have my Google calendar syncing with perhaps hundreds of
  events. However, there's no reason that this should cause indicator-
  datetime to use more RSS; it shouldn't be keeping these in memory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp