Jason Tackaberry <[EMAIL PROTECTED]> writes: > However, after repeating the procedure I used to cause the above > problem, I got this message on the terminal: > > Xlib: unexpected async reply (sequence 0x3a1ae)! > > And the process started to eat all available CPU.
You're using threads? > Now I suppose it's possible I am doing something wrong, but the > offending code can iterate thousands of times before I see any > problems. That's quite common with thread-related bugs. Havoc _______________________________________________ gtk-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/gtk-list
