nanogui: Thread: GsHandleClient request too large


[<<] [<] Page 1 of 1 [>] [>>]
Subject: GsHandleClient request too large
From: ####@####.#### ####@####.####
Date: 30 Nov 2006 17:48:20 +0000
Message-Id: <J9K1FZ$073F2F27D82ED6391E72E83CC6069222@libero.it>

Hi, i have an ARM processor with uClib and kernel 2.6.8.
I installed nanox on it and i integrated it with my graphic application. But i have one big problem:

1. when i add more graphic call to draw elements nano-x run less speedly and after a moment stops.

The error on the console is:
GsHandleClient request too large: 12320684 > 30000

I see the source code of nano-x but i don't understand which is the step to fall into this error.

Can you help me?






------------------------------------------------------
Cosa fai a Natale e Capodanno? Parti con Expedia: prima prenoti, piĆ¹ risparmi! Scopri subito tutte le offerte!
http://click.libero.it/Expedia_30nov06


Subject: Re: [nanogui] GsHandleClient request too large
From: "Greg Haerr" ####@####.####
Date: 30 Nov 2006 23:57:44 +0000
Message-Id: <015901c714db$4b2ad4c0$6401a8c0@winXP>

> 1. when i add more graphic call to draw elements nano-x run less speedly
and after a moment stops.
The error on the console is:
GsHandleClient request too large: 12320684 > 30000

There's an internal buffer which limits the maximum size of
data (including image data) that can be sent across from
client to server in one packet.  I've attached Martin's
patch which eliminates this restriction.  See if that
helps.

Regards,

Greg

[Content type application/octet-stream not shown. Download]
Subject: GsHandleClient request too large
From: Roberto Bielli ####@####.####
Date: 1 Dec 2006 08:25:49 +0000
Message-Id: <456FE76A.5070601@axelsw.it>

Thanks for the response of yesterday about .
This is the new mail on which i write you.
The problem is not resolved while i'm not using bitmap.

I write under the old problem:

 >>Hi, i have an ARM processor with uClib and kernel 2.6.8.
 >> I installed nanox on it and i integrated it with my graphic 
application. But i have one big problem:
 >>1. when i add more graphic call to draw elements nano-x run less 
speedly and after a moment stops.
 >>The error on the console is:
 >> GsHandleClient request too large: 12320684 > 30000
 >>I see the source code of nano-x but i don't understand which is the 
step to fall into this error.
 >>Can you help me?

I explain better my situation.
I have two threads, one that write the screen with the nano-x functions 
( like GrArea, GrFill, etc. ), one that calls the
GrCheckNextEvent() to catch the events and release the messages.
I seems that if i add more calls ( ex. GrArea ) before calling the 
GrCheckNextEvent  the system give that error. I have to make these calls.
I have also try to add GrFlush after every GrArea calls but never change.

Can you Help Me ?



Subject: Re: [nanogui] GsHandleClient request too large
From: "Greg Haerr" ####@####.####
Date: 6 Dec 2006 23:04:58 +0000
Message-Id: <06ae01c7198a$ffba7720$0300a8c0@RDP>

:  >> GsHandleClient request too large: 12320684 > 30000


: I have two threads, one that write the screen with the nano-x functions 
: ( like GrArea, GrFill, etc. ), one that calls the
: GrCheckNextEvent() to catch the events and release the messages.
: I seems that if i add more calls ( ex. GrArea ) before calling the 
: GrCheckNextEvent  the system give that error. I have to make these calls.
: I have also try to add GrFlush after every GrArea calls but never change.

Roberto - 

The error above hasn't to do with whether or not you
cal GrCheckNextEvent.  It has to do with the maximum
allowed data packet the server can receive.  As
shown, you are above the max.  You need to debug
and find which function the server is executing when it
gives that error.  You can un-comment a printf()
in the GsHandleClient function to find this out.  We
can then work on a solution.

If your applications/multiple threads issue causes 
different requests to be created as a result of timing,
then there is that much more complexity to debug.

The GrArea routines sends data from the server to the
client, and shouldn't be the cause of the error.

Regards,

Greg

Subject: Re: [nanogui] GsHandleClient request too large
From: ####@####.#### ####@####.####
Date: 7 Dec 2006 08:23:51 +0000
Message-Id: <J9W9ZC$FAFD85054B77525FF340AEB55D70E42D@libero.it>

Hi Greg,

thanks for your help, i solved the problem enabling the threadsafe options in nano-x config file, and then i recompile it.









> :  >> GsHandleClient request too large: 12320684 > 30000
> 
> 
> : I have two threads, one that write the screen with the nano-x functions 
> : ( like GrArea, GrFill, etc. ), one that calls the
> : GrCheckNextEvent() to catch the events and release the messages.
> : I seems that if i add more calls ( ex. GrArea ) before calling the 
> : GrCheckNextEvent  the system give that error. I have to make these calls.
> : I have also try to add GrFlush after every GrArea calls but never change.
> 
> Roberto - 
> 
> The error above hasn't to do with whether or not you
> cal GrCheckNextEvent.  It has to do with the maximum
> allowed data packet the server can receive.  As
> shown, you are above the max.  You need to debug
> and find which function the server is executing when it
> gives that error.  You can un-comment a printf()
> in the GsHandleClient function to find this out.  We
> can then work on a solution.
> 
> If your applications/multiple threads issue causes 
> different requests to be created as a result of timing,
> then there is that much more complexity to debug.
> 
> The GrArea routines sends data from the server to the
> client, and shouldn't be the cause of the error.
> 
> Regards,
> 
> Greg
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 
> 

Roberto Bielli - 3200777027 



------------------------------------------------------
Passa a Infostrada. ADSL e Telefono senza limiti e senza canone Telecom
http://click.libero.it/infostrada07dic06


[<<] [<] Page 1 of 1 [>] [>>]


Powered by ezmlm-browse 0.20.