*** This bug is a duplicate of bug 772340 ***
https://bugs.launchpad.net/bugs/772340
** This bug has been marked a duplicate of bug 772340
e-calendar-fact and indicator-datet consumes 2,6GB Memory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Unfortunately, I rely on the event notifications to tell me when
meetings are coming up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/782468
Title:
indicator-datetime excess memory usage
To manage
David: I've disabled "Coming events from evolution" feature in the
indicator settings dialog, and that has resolved the memory leaks issue
for me. It's not a real fix, but a reasonable workaround for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
This is still an issue. Please let us know what sort of feedback we can
give to help get this bug resolved. Sometime I come back to my machine
in the morning and I have a gig of RAM eat up by indicator-datetime.
** Changed in: indicator-datetime (Ubuntu)
Status: Expired => Confirmed
--
[Expired for indicator-datetime (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: indicator-datetime (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Attachment added: "valgrind second run attempt"
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/782468/+attachment/154/+files/valgrind-with-trace-children-run2.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ok, so I replaced the /usr/lib/indicator-datetime/indicator-datetime-
service with a bash script that calls binary through valgrind (probably
what I should've done in the first place).
I see a lot of calendar fetching for repeat events in my evolution
calendar source.
See attachment for log.
--
right, it seems there was nothing trying to load the indicator,
"(process:2721): libindicator-WARNING **: No watchers, service timing
out."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/782468
Title:
** Attachment added: "valgrind --leak-check=full --trace-children=yes run."
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/782468/+attachment/2221464/+files/valgrind-with-trace-children.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I renamed the binary, and ran valgrind with the following options. I
don't think it's getting useful info (mostly startup/init stuff) and
then shuts down immediately.
valgrind --leak-check=full--trace-children=yes /usr/lib/indicator-
datetime/indicator-datetime-service.valgrind
See output in atta
one way to do it is to rename indicator-datetime-service to indicator-
datetime-service.bin and write a small indicator-datetime-service
wrapper calling the valgrind command on the real binary
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Services seem to get auto-started (at least when I kill /usr/lib
/indicator-datetime/indicator-datetime-service, I see another instance
load immediately). This makes valgrind'ng a little tricky.
If you can let us know how to enable debugging/run valgrind on services,
that would be great. Thanks.
@Ted: Could you please provide the command line entry to run Valgrind to
capture the necessary information? which indicator-datetime-service
does not bring up any results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Could you please attach a valgrind log to this bug? That'd be the best
way to see what is happening on your system:
https://wiki.ubuntu.com/Valgrind
Thank you.
** Changed in: indicator-datetime (Ubuntu)
Status: New => Incomplete
** Changed in: indicator-datetime (Ubuntu)
Importance:
After pulling down the source code to the indicator, I noticed a lot of
code dealing with fetching Evolution appointments.
After disabling that functionality in the settings and restarting the
indicator-datetime service ( left the machine on over the weekend), I no
longer observed the leak.
My ev
** Attachment added: "pmap output of indicator-datetime app"
https://bugs.launchpad.net/bugs/782468/+attachment/2127675/+files/pmap.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/782468
Title:
16 matches
Mail list logo
