[Bug: 21.4.12] xemacs: X Error of failed request: BadWindow(invalid Window parameter)
Ben Wing
ben at 666.com
Tue Nov 16 19:14:12 EST 2004
> about once a week or so i get the following errors.
> ----------------------------------------------------
>
> xemacs: X Error of failed request: BadWindow (invalid Window
> parameter)
> Major opcode of failed request: 25 (X_SendEvent)
> Resource id in failed request: 0x28284f0
> Serial number of failed request: 2529824
> Current serial number in output stream: 2529825
> Xlib: unexpected async reply (sequence 0x269a21)!
>
> xemacs: X Error of failed request: BadWindow (invalid Window
> parameter)
> Major opcode of failed request: 18 (X_ChangeProperty)
> Resource id in failed request: 0x28284f0
> Serial number of failed request: 2529823
> Current serial number in output stream: 2529825
> -----------------------------------------------------
>
> when this happens xemacs locks up and i have to kill the process.
>
> this first started about 5 months ago and was only occasional
> (once a month so so) but now it happens about every other week.
>
> i do not know what i was doing when this happened all i can
> say is that when i went to xemacs to look at a file it was
> hung. this is typically the case. one minute it is fine and
> the next its hung.
We need a backtrace to diagnose this. Could you put in an abort() in
device-x.c directly after the call to XmuPrintDefaultErrorMessage (disp,
event, stderr)? Then use a debugger to get a backtrace from the core dump.
More information about the XEmacs-Beta
mailing list