Re: X sequence lost

I see the "async reply" problem mostly upon starting a subprocess, like igrep. Could this be related to Ben's subprocess changes? Xlib: unexpected async reply (sequence 0xd03)! Xlib: sequence lost (0x101c2 > 0xd03) in reply type 0x99! Xlib: sequence lost (0x10000 > 0xd03) in reply type 0x0! xemacs: X Error of failed request: 0 Major opcode of failed request: 3 (X_GetWindowAttributes) Serial number of failed request: 0 Current serial number in output stream: 3331 Anybody got any idea on how I can debug this? -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla