crash on X-System ..

[GoogleCodeExporter]

This happens on my Ubuntu system at work. 
Quite often (each second time) Toped crashes with following error messages 
immediately after the start:

toped: ../../src/xcb_io.c:140: dequeue_pending_request: Assertion `req == 
dpy->xcb->pending_requests' failed.

or 

toped: Fatal IO error 0 (Success) on X server :0.0.
toped: ../../src/xcb_io.c:221: poll_for_event: Assertion `(((long) 
(event_sequence) - (long) (dpy->request)) <= 0)' failed.

or even sometimes with 

The program 'toped' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
  (Details: serial 19882 error_code 14 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

I'm very aware that this happens maybe to my system only .. thus, I'll give 
this bug very low priority. Also my system isn't updated quite a long time and 
the behaviour could be completely different after an upgrade.

Nevertheless I want to point out that this "might" be a bug in Toped. I had the 
feeling that the crashes are related to the size of the TLL code which is given 
as a parameter. So, this might be happen on slow machines only .. maybe 
something related to the thread-handling .. just a guess.

My X-Server: is xorg-1.10
My Graphic-card: GeForce 8400GS

Thanks in advance
armin

Original issue reported on code.google.com by analogc...@gmx.net on 20 Nov 2012 at 12:58

[GoogleCodeExporter]

Well if it's crashing - it means it's a bug, another question is where exactly 
and how easy is to diagnose/reproduce it.

Some questions: 
- what command line options you're using if any? Did you try to change with 
them?
- if you're running in "normal" graphical mode - do you see any window 
poping-up at all?

It does look like a thread problem as you're mentioned but let's not jump to 
conclusions too early.

Original comment by krustev....@gmail.com on 21 Nov 2012 at 12:13