On Mon, Dec 29, 2008 at 7:07 AM, Joseph Rawson <umebos...@gmail.com> wrote: > python: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) > ((xcb_req) - (dpy->request)) >= 0)' failed. Is there any more to the message? I would guess its a failed lock, ( but, it doesn't look like pygame specifically. ) > > This only seems to happen when I'm testing on my local desktop, using > windowed, instead of fullscreen mode. On my desktop, I get more xcb_lock > errors, than I do freezes. > > The application is to be run on a dedicated machine, and the signal is to go > through the tv-out of the video card and be split among several tv's. I am > using debian/lenny for the OS of the machine, and X11 for the display (to be > able to use the tv-out). I'm saying this, because I believe that the bug may > be in X, or the way that X is being used by either sdl or pygame, although > I'm not really sure. Since I'm new to programming with pygame, it's very > possible that the bug is in my code, and I have overlooked something > important. > > I test the system using virtualbox, and on the VM, the xcb_lock error never > occurs, rather, the scene will freeze, and the cpu will be pegged at 100%.
Probably doesn't matter, but, you could try pygame.time.get_ticks() for your getting ticks function. (someone smarter will be along) -- Jake
