答复: Help! Xlib error

[Ma, Qingyu (GE Healthcare)]

Because my application is huge, and I'm not quite sure  which part cause this issue.
I'm trying to reduce the range, but it's difficult to reproduce the issue. 
During the long time run,  two kinds of operation related with Xserver are executed in the loop, one is openGL operation, another is faking key event to control key LED.
Could you please give me some direction that which part may cause the issue?


Best Regards,
Ma Qingyu

-----邮件原件-----
发件人: Peter Hutterer [mailto:peter.hutterer at who-t.net] 
发送时间: 2010年5月5日 19:39
收件人: Ma, Qingyu (GE Healthcare)
抄送: xorg at lists.freedesktop.org
主题: Re: Help! Xlib error

On Wed, May 05, 2010 at 04:16:02PM +0800, Ma, Qingyu (GE Healthcare) wrote:
> My application use openGL to draw some image on window, and modify led 
> state on keyboard through faking key event. The operations are 
> executed at 33ms interval.
> If I add some system pressure, after long time execution, there is a 
> rare possibility to occur below two errors.
>  
> #1
> XIO: fatal IO error 0 (Success ) on X server "-"
>        after 21 requests (9 known processed) with 0 event remaining.
>  
> #2
> X Error of failed request:  BadLength (poly request too large or 
> internal Xlib length error)
>   Major opcode of failed request:  148 (XTEST)
>   Minor opcode of failed request:  2 (X_XTestFakeInput)
>   Serial number of failed request:  16
>   Current serial number in output stream:  20 X Error of failed request:
> BadLength (poly request too large or internal Xlib length error)
>   Major opcode of failed request:  148 (XTEST)
>   Minor opcode of failed request:  2 (X_XTestFakeInput)
>   Serial number of failed request:  15
>   Current serial number in output stream:  20
>  
>  
> I didn't find any clue in Xorg.0.log and message log.
> The system pressure is, Mem: 40MB free and 500MB swap is used, CPU: 
> 95%, continuous disk writing, opengl demo(moving gear).
>  
> Could you please tell me what may cause these two errors?  It's urgent.
> Thanks very much.

hmm. BadLength is usually a server or an Xlib bug. Can you provide the code that reproduces this issue?

Cheers,
  Peter