Re: [gDesklets] 0.36.3 leaking memory?!

[Bjoern Koch <H Humpel gmx de>]

Hi there,

hmm... the only thing I can think of right now is the fix of bug #260288
(https://bugs.launchpad.net/gdesklets/+bug/260288 , see comment #4):

"Now the image gets re-rendered everytime (even if width and height stay
the same) and everything is working fine.
I am not sure if this has a significant impact on the performace of
gDesklets... ?!"

Maybe someone can "de-fix" it (see rev. #142 in the 0.3x branch) and
test it ?!

Greetings, Bjoern


Am 09.03.2011 10:59, schrieb Ronny Lorenz:
> Hi Folks,
> 
> I recently upgraded to version 0.36.3 and experience an increasing
> amount of memory being used by the gdesklets-daemon :(
> I tried to pinpoint the source of the leak by removing my ~/.gdesklets
> dir and starting a plain new session.
> I then tried adding the displays I formerly used one by one and found
> that when I have just the "Genesis" display (v 0.2) and moved the mouse
> over the default starter (the home icon) to activate pulsing of the icon
> the gdesklets-daemon starts to accumulate memory.... just slowly but
> constantly.
> I dont know much about python and gow to best trackdown the real problem
> but this behavior filled my memory with 1.6GB garbage in 6 days uptime
> (with only 3 displays loaded, 2x Genesis and 1x Clock)
> 
> Any suggestions on how I should proceed/deal with this behavior or
> anybody who can reproduce it?
> 
> I use ArchLinux with Python 3.2
> 
> I had no such problems using gDesklets 0.36.2
> 
> greetz
> 
> ronny
> 
> _______________________________________________
> gdesklets-list mailing list
> gdesklets-list gnome org
> http://mail.gnome.org/mailman/listinfo/gdesklets-list
>