lcd4linux-devel

[Lcd4linux-devel] Memory usage grows when using images

[Magne <tor...@st...>]

Hi,
When there are image widgets enabled in the layout, the memory usage of
lcd4linux grows steadily until there is nothing left and the process is
killed. Consumption grows faster when image update times are low. Could
it be that memory is not freed after rereading the image file?
Additionally, setting the update delay to 0 does not make the image
static, but makes updates go as fast as possible.

I'm using the current cvs-version and a T6963 240x128 display.

Thanks in advance

Magne T=F8rresen

Re: [Lcd4linux-devel] Memory usage grows when using images

[Michael R. <re...@eu...>]

Hi Magne,

> When there are image widgets enabled in the layout, the memory usage of
> lcd4linux grows steadily until there is nothing left and the process is
> killed. Consumption grows faster when image update times are low. Could
> it be that memory is not freed after rereading the image file?

uh-oh :-)

Thnaks for pointing this out, should be fixed in CVS (a gdImageDestroy()
was missing)

> Additionally, setting the update delay to 0 does not make the image
> static, but makes updates go as fast as possible.
Fixed in CVS, too. Thanks again!

Please test and give some feedback!


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [Lcd4linux-devel] Memory usage grows when using images

[Magne <tor...@st...>]

On Thu, 28 Sep 2006 06:13:39 +0200
Michael Reinelt <re...@eu...> wrote:

> Please test and give some feedback!

It's been running for several hours now, with no sign of any leaks.
Good work :) Thank you!

Feature request: A secondary update timer for image widgets, only
evaluating the visible-expression, would be much appreciated. This way
the imagefile will not be reread when one only wants to toggle the
visibility of an image, saving precious cycles :)

Regards,
Magne T=F8rresen

Re: [Lcd4linux-devel] Memory usage grows when using images

[Michael R. <re...@eu...>]

> It's been running for several hours now, with no sign of any leaks.
> Good work :) Thank you!
Great!

> Feature request: A secondary update timer for image widgets, only
> evaluating the visible-expression, would be much appreciated. This way
> the imagefile will not be reread when one only wants to toggle the
> visibility of an image, saving precious cycles :)

Well, I decided not to use two timers (handling may be complicated), but
used a new property called 'reload'. When reload is 0 (zero), the image
will be loaded only once, and on update only 'visible' and 'inverted'
will influence the display. When 'reload' evaluates to 1, the image will
be read again.

I also changed lots of internal stuff (switched the whole image widget
to the new 'properties' data structure), so there may be lots of bugs
:-( As I don't have a graphical display ready for testing, this was kind
of 'blind hacking', so any tests and feedback would be greatly appreciated!


bye, Michael

-- 
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781

Re: [Lcd4linux-devel] Memory usage grows when using images

[Magne <tor...@st...>]

On Fri, 29 Sep 2006 07:15:33 +0200
Michael Reinelt <re...@eu...> wrote:

> > Feature request: A secondary update timer for image widgets, only
> > evaluating the visible-expression, would be much appreciated. This way
> > the imagefile will not be reread when one only wants to toggle the
> > visibility of an image, saving precious cycles :)
>=20
> Well, I decided not to use two timers (handling may be complicated), but
> used a new property called 'reload'. When reload is 0 (zero), the image
> will be loaded only once, and on update only 'visible' and 'inverted'
> will influence the display. When 'reload' evaluates to 1, the image will
> be read again.

Just a little difference in terminology; the functionality here is exactly =
what I wanted :)

As for testing; I have not found any problems so far. It works just as desc=
ribed. Thanks!=09

Regards,
Magne T=F8rresen