[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#16676: 24.3.50; Repeated but random hang
From: |
Eli Zaretskii |
Subject: |
bug#16676: 24.3.50; Repeated but random hang |
Date: |
Sat, 08 Feb 2014 19:47:53 +0200 |
> From: "Jan D." <jan.h.d@swipnet.se>
> Date: Sat, 8 Feb 2014 17:40:21 +0100
> Cc: Lars Ingebrigtsen <larsi@gnus.org>,
> "16676@debbugs.gnu.org" <16676@debbugs.gnu.org>
>
> The io error handler is only called for fatal errors. Any system call
> related to io in Xlib that fails
> triggers a call to the error handler. Xlib can not recover from this, so the
> connection is lost.
> If something writes garbage into Xlibs data, anything can happen.
Is it wise to issue further X calls in this situation? Maybe we
should skip X calls when we delete the frame as result of such
problems.
- bug#16676: 24.3.50; Repeated but random hang, Lars Ingebrigtsen, 2014/02/06
- bug#16676: 24.3.50; Repeated but random hang, Eli Zaretskii, 2014/02/07
- bug#16676: 24.3.50; Repeated but random hang, Dmitry Antipov, 2014/02/07
- bug#16676: 24.3.50; Repeated but random hang, Lars Ingebrigtsen, 2014/02/07
- bug#16676: 24.3.50; Repeated but random hang, Eli Zaretskii, 2014/02/08
- bug#16676: 24.3.50; Repeated but random hang, Lars Ingebrigtsen, 2014/02/08
- bug#16676: 24.3.50; Repeated but random hang, Eli Zaretskii, 2014/02/08
- bug#16676: 24.3.50; Repeated but random hang, Jan D., 2014/02/08
- bug#16676: 24.3.50; Repeated but random hang,
Eli Zaretskii <=
- bug#16676: 24.3.50; Repeated but random hang, Jan Djärv, 2014/02/08