RE: Hard loop in XtAppPending when X server killed

On Fri, 7 Jun 2002, andy(a)xemacs.org wrote: I think this problem occurs because of delete_device event handling. The broken x connection causes the IO_error_handler to be called. I've been annoyed by this problem for a while. I have it in my (very long) queue to verify if this is the problem and propose a fix. If somebody else wants to look at it though... I attached part of a previous message on the issue.... -jeff Date: Tue, 23 Apr 2002 22:34:55 -0400 Subject: Re: gnuclient *feature* -- crash when frames lose X connection Cc: XEmacs Beta List <xemacs-beta(a)xemacs.org&gt; The function x_IO_error_handler enqueues a magic eval delete_device event. Supposedly, doing this magic event will cause the device to exit. After event is enqueued, the device is marked as being deleted. int x_IO_error_handler (Display *disp) { ... if (d) enqueue_magic_eval_event (io_error_delete_device, dev); DEVICE_X_BEING_DELETED (d) = 1; Fthrow (Qtop_level, Qnil); ... } Then we go over to handle_magic_event. The first thing that this code does is checks to see if the frame is being deleted. If it is, magic event function returns, and does not actually process the event. Might this be the problem? static void emacs_Xt_handle_magic_event (Lisp_Event *emacs_event) { /* This function can GC */ XEvent *event = &emacs_event->event.magic.underlying_x_event; struct frame *f = XFRAME (EVENT_CHANNEL (emacs_event)); if (!FRAME_LIVE_P (f) || DEVICE_X_BEING_DELETED (XDEVICE (FRAME_DEVICE (f)))) return; switch (event->type) -jeff