I reported the large memory leak in clock-applet:

https://bugzilla.redhat.com/show_bug.cgi?id=952763

(TLDR: clock-applet grows by 1GB/day when reporting weather)

Since clock-applet is a default install on every Fedora, I thought this would be widely reported---it essentially makes the system unusable within a day or two if you run into this problem---but that doesn't seem to be the case. I guess people don't see it because nobody reconfigures clock-applet.

Anyway, I am looking for a way to debug this: I tried attaching GDB to the running process but the results are unreliable (see BZ). I couldn't figure out how to run valgrind on the executable: it has to be run in the context of the Gnome panel, so how do I tell it to run 'valgrind /usr/libexec/clock-applet', and how do I get access to the results?
Is there another way?
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Reply via email to