After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 343912 - clock applet leask memory
clock applet leask memory
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: clock
git master
Other All
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-06-05 13:20 UTC by Ajay Gautam
Modified: 2006-10-02 14:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Ajay Gautam 2006-06-05 13:20:37 UTC 
Please describe the problem:
Left gnome desktop running over the weekend. Process clock-applet uses the 2nd largest amount of memory. Here is the before and after of killing it:

Before:
$ ps aux | grep clock
agautam  13107  0.0  8.7 162888 90456 ? Sl Jun02 1:16 /usr/libexec/clock-applet

$ kill 13107
$ ps aux | grep clock
agautam  10785  5.0  0.9  22836  9960 ? S  09:19 0:00 /usr/libexec/clock-applet


Steps to reproduce:


Actual results:


Expected results:
No memory leaks.

Does this happen every time?
Yes

Other information:
This could be cause by the evolution connector (http://bugzilla.gnome.org/show_bug.cgi?id=335423)
Comment 1 Danielle Madeley 2006-08-07 04:40:22 UTC 
Reassigning to panel.
Comment 2 Vincent Untz 2006-08-07 21:53:10 UTC 
Ajay: would it be possible to tell us if it still does this when the new evolution packages are packaged?
Comment 3 Ajay Gautam 2006-08-10 17:23:37 UTC 
(In reply to comment #2)
> Ajay: would it be possible to tell us if it still does this when the new
> evolution packages are packaged?
> 

Sure. Which evolution version ahould I look out for ?
Comment 4 Vincent Untz 2006-08-11 12:03:17 UTC 
Ajay: evolution 2.6.3 or, if you can upgrade, 2.7.3.

Marking as NEEDINFO until you can try.
Comment 5 Ajay Gautam 2006-10-02 14:17:13 UTC 
I am no longer using evolution / exchange-connector. Its too frustrating (even compared to an remote-desktop connection for outlook). Resolving this issue.