It seems that xemacs-21.5-b16 does not suffer from it. It does print error
messages but does not hang.
xemacs-21.5-b16: X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 3 (X_GetWindowAttributes)
Resource id in failed request: 0x0
Serial number of failed request: 5292
Current serial number in output stream: 5293
intro: "SJT" == Stephen J Turnbull <stephen(a)xemacs.org> writes:
>>>>> "Glynn" == Glynn Clements
Glynn> Nickolay Pakoulin wrote:
>> XEmacs 21.4-14 hangs when editres client asks 'Select
widget in client'.
>> XEmacs 21.5 does not hang. XEmacs prints in the console: xemacs: X Error
>> of failed request: BadWindow (invalid Window parameter)
Glynn> I get the same result here (BadWindow error for X_GetWindowAttributes,
Glynn> XEmacs hangs).
SJT> Now this is interesting. Glynn, so you think there's a chance that this
SJT> is a repeatable instance of whatever it is that causes the intermittent
SJT> BadWindow bugs we see?
SJT> What options do we have? Our own error handler? Can we force the
SJT> widget to be realized and just not map/manage it?
SJT> -- Institute of Policy and Planning Sciences
University of Tsukuba Tennodai 1-1-1
SJT> Tsukuba 305-8573 JAPAN Ask not how you can "do" free software
SJT> ask what your business can "do for" free software.