Just started updating my platformer/2d engine to use some extra threads, Ie, one screen updates screen and keeps cleaning my video memory and other variables of the Engine and underlying data along with my cache system for searching through arrays faster (Commonly used ones anyway) and I cam across an issue:

Code:
SmashMan: ../../src/xcb_io.c:249: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
Aborted
Along with exit code 134, which to me, makes no sense at all. I'm considering using some proof of concept code I used when I first explored multi-threading that tracks EVERY resource and manages what accesses what and when but it can't do speed for sqwat... That is, if it evern runs; since it was only proof of concepts its rather sloppy and, erm, a pain to debug/use for anything where reliability matters... Any thoughts?