From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 50043@debbugs.gnu.org
Subject: bug#50043: 28.0.50; USABLE_SIGOI undef code paths do not work correctly
Date: Wed, 17 Nov 2021 09:19:27 -0500 [thread overview]
Message-ID: <c1cca353-7fe9-7d45-114f-7643ebbc0e39@cornell.edu> (raw)
In-Reply-To: <83sfvuzzy5.fsf@gnu.org>
On 11/17/2021 8:14 AM, Eli Zaretskii wrote:
>> Date: Tue, 16 Nov 2021 18:06:51 -0500
>> Cc: larsi@gnus.org, 50043@debbugs.gnu.org
>> From: Ken Brown <kbrown@cornell.edu>
>>
>> Are you talking about having x_get_foreign_selection call
>> wait_reading_process_output in a loop?
>
> Yes.
>
>> That would fix this particular bug, but I was thinking of trying to
>> solve a more general problem.
>
> What is that more general problem, and when does it rear its ugly
> head?
The problem is that whenever wait_reading_process_output needs to repeatedly
check for input (i.e., read_kbd || !NILP (wait_for_cell) == true), it can get
stuck in select for up to 2 seconds on systems without USABLE_SIGIO. (2 arises
here because it's the default value of polling-period.)
I don't know offhand when it rears its ugly head aside from the X selection case
we're discussing. We would only know about it if someone notices an unexpected
delay, finds a recipe for reproducing it, and reports it as a bug, as happened
here with bug#29170, which is what led to the present bug report. And look how
long it took before the cause of that delay was discovered.
So I think it's better to fix the general (potential) problem, not just the X
selection case.
Ken
next prev parent reply other threads:[~2021-11-17 14:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 11:56 bug#50043: 28.0.50; USABLE_SIGOI undef code paths do not work correctly Lars Ingebrigtsen
2021-08-13 13:16 ` Eli Zaretskii
2021-08-13 14:31 ` Lars Ingebrigtsen
2021-08-13 15:51 ` Eli Zaretskii
2021-08-14 11:52 ` Lars Ingebrigtsen
2021-11-15 15:19 ` Ken Brown
2021-11-15 17:24 ` Eli Zaretskii
2021-11-15 19:26 ` Ken Brown
2021-11-16 17:44 ` Eli Zaretskii
2021-11-16 23:06 ` Ken Brown
2021-11-17 7:41 ` Lars Ingebrigtsen
2021-11-17 14:25 ` Ken Brown
2021-11-17 13:14 ` Eli Zaretskii
2021-11-17 14:19 ` Ken Brown [this message]
2021-11-17 14:34 ` Eli Zaretskii
2021-11-17 14:59 ` Ken Brown
2021-11-17 16:56 ` Eli Zaretskii
2021-11-17 17:25 ` Ken Brown
2021-11-17 17:37 ` Eli Zaretskii
2021-11-17 17:45 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c1cca353-7fe9-7d45-114f-7643ebbc0e39@cornell.edu \
--to=kbrown@cornell.edu \
--cc=50043@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).