Re: [Bug: 21.4.14] XEmacs hangs when doing networking
Jan Rychter wrote:
> The common recurring theme is the two messages that appear on
the
> console that XEmacs was started from:
>
> X Error of failed request: BadWindow (invalid Window parameter)
> Major opcode of failed request: 25 (X_SendEvent)
> Resource id in failed request: 0xe009ba
> Serial number of failed request: 593927
> Current serial number in output stream: 594059
> Xlib: unexpected async reply (sequence 0x9108b)!
>
> xemacs-21.4.14: X Error of failed request: BadWindow (invalid Window parameter)
> Major opcode of failed request: 18 (X_ChangeProperty)
> Resource id in failed request: 0xe009ba
> Serial number of failed request: 593926
> Current serial number in output stream: 594059
[umpteen or so crashes later, having lost some data along the way]
Can I do anything else to help resolving this bug?
The following may produce useful information, but they may involve
more inconvenience than you can accept:
Log all calls to x_reply_selection_request(), including the serial
numbers of the outbound events (using NextRequest()).
Add XSync() calls within x_reply_selection_request(), and set a
breakpoint (in gdb) on x_error_handler().
Add XSync() calls after all calls to XChangeProperty(), and set a
breakpoint on x_error_handler() (in the event that the previous
suggestion doesn't catch the error).
Is this a known problem, or is it just me?
You certainly aren't the only person to report it.
Is anyone working on this?
I don't think so.
I have a feeling this could be related to the resolver.
How so?
--
Glynn Clements <glynn.clements(a)virgin.net>