unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: rajeev.jnk@sivalik.com, 49682@debbugs.gnu.org
Subject: bug#49682: 27.2.50; accept-process-output within accept-process-output hangs emacs
Date: Fri, 23 Jul 2021 21:30:54 +0300	[thread overview]
Message-ID: <f65a0301-d52b-c5a8-408f-cf65000424e7@yandex.ru> (raw)
In-Reply-To: <83fsw6528f.fsf@gnu.org>

On 22.07.2021 08:47, Eli Zaretskii wrote:
>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Cc: Rajeev N <rajeev.jnk@sivalik.com>,  49682@debbugs.gnu.org
>> Date: Wed, 21 Jul 2021 23:32:16 +0200
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>>> (let () (run-with-timer 0 nil #'url-retrieve "https://www.gnu.org/"
>>>> #'ignore) (diary-mail-entries))
>>>
>>> Don't do that, because it will hurt.  Mixing timers with subprocesses
>>> is asking for trouble.
>>
>> That's not my experience, really -- url-queue.el is based around firing
>> off `url-retrieve' from timers, and I've never seen any problems.
> 
> Sheer luck, IMO.
> 
> I don't really understand the need to run subprocesses from timers,
> since subprocess support already includes async operation and built-in
> time-outs.

This is a fairly common configuration. Consider a minimal IDE setup:

1. Code completion popup which is shown when Emacs is idle for XX ms.
2. Eldoc hints which are shown at YY ms after the user stops typing.

When both are implemented using HTTP calls, you get "timers with 
subprocesses".

In fact, I have a configuration like that (based on url.el) and get an 
occasional strong freeze (one that requires 3 C-g's to get out of) about 
once every 1-2 weeks. Haven't found a solid repro so far, so if the 
reporter has something stable-ish, I'll be following this report intently.





  reply	other threads:[~2021-07-23 18:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 14:58 bug#49682: 27.2.50; accept-process-output within accept-process-output hangs emacs Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-21 15:14 ` Lars Ingebrigtsen
2021-07-21 16:14   ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-21 16:18     ` Lars Ingebrigtsen
     [not found]       ` <87tukntz2m.fsf@hm.sivalik.com>
2021-07-21 16:40         ` Lars Ingebrigtsen
2021-07-23 17:00       ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-24 10:28         ` Lars Ingebrigtsen
2021-07-24 10:46           ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-26 18:58         ` Dmitry Gutov
2021-07-26 19:54           ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-26 20:22             ` Dmitry Gutov
2021-07-26 20:55               ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-27 14:13                 ` Dmitry Gutov
2021-07-27 17:22                   ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-27 17:35                     ` Eli Zaretskii
2021-07-27 21:40                       ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-28 16:12                         ` Eli Zaretskii
2021-07-28 17:12                           ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-06 16:55                           ` Robert Pluim
2021-07-21 19:29 ` Eli Zaretskii
2021-07-21 21:32   ` Lars Ingebrigtsen
2021-07-21 21:53     ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-22  5:47     ` Eli Zaretskii
2021-07-23 18:30       ` Dmitry Gutov [this message]
2023-11-06 17:14 ` LdBeth
2023-11-06 17:39   ` Eli Zaretskii
2023-11-06 20:27     ` LdBeth
2023-11-07  9:24       ` Michael Albinus
2023-11-08 15:50     ` Kazuhiro Ito
2023-11-08 16:37       ` Eli Zaretskii

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=f65a0301-d52b-c5a8-408f-cf65000424e7@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=49682@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=rajeev.jnk@sivalik.com \
    /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).