Re: [gDesklets] 0.36.3 leaking memory?!

Hi Bjoern,

this may be it... I found that gdk_pixbuf_scale_simple() returns a copy... and 'scaled' (in the appropriate line of utils/render.c) seems to be free'd only if the width or height has changed...
I will try and test it if I find out how to checkout the sources ;)

greetings, ronny

On 03/09/2011 03:19 PM, Bjoern Koch wrote:
Hi there,

hmm... the only thing I can think of right now is the fix of 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
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



gdesklets-list mailing list
gdesklets-list gnome org

gdesklets-list mailing list
gdesklets-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]