[Lcdproc] possible bug and/or limitation

[Martin T Jones]

On 13/10/11 15:12, Pedro Peixoto wrote:
> hello
>
> This email is to address a possible bug and/or limitation in the
> application lcdproc version 0.5.4, on which i would get if possible
> your support in order to solve the problem found.
>   I'm developing an client application based on lcdproc demo client,
> to cpmunicate with a server previously started. This application
> has only a single client with a single display where are shown a list
> of information updated in a pre-determined period. The function
> structure used for sending messages from client to server is as
> follows:
>  - Create screen
>  - Create Widgets
>  - Endless loop:
> >  sleep 500mS
> >  set widget #1
> >  sleep 10mS
> >  set widget #2
> >  sleep 10mS
> ...
> >  set widget #11
> >  sleep 10mS
>    Repeat loop
>
> Basicly, desired variables are updated at 500mS rate with an interval
> of 10mS for each message sent from client to server
> This is important to understand the problem. This sequence works
> perfectly for an interval of 320 minutes ± 5min. At this time
> the serever stops writing to display and receiving messages
> (sock_printf function) that is used for sending messages, which
> returns
> an error. After restarting the server everything works again this the
> 320 minute time elapses again.
>   Several tests have been done in order to better understand the
> problem source. If the 10mS sleep betwin messegas is removed, the time
> to server crash becomes 240 min ± 5 min. In face of that, it seems
> that the server has some limitation on the quantity (??) of messages
> that can be handled or even a bug in an buffer allocation that is not
> properly cleared/released.
>
> I would like to have your feedback on this issue, and any clue to 
> solve it.
>
>
> Thanks in advance for your support,
> Pedro Peixoto

Do you read the messages from LCDd? you don't mention them in your
email, if you do not the socket buffer will fill up and give the symptoms
you describe. See:

http://lcdproc.sourceforge.net/docs/lcdproc-0-5-4-dev.html#language-messages

Hope this helps.

Martin