From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: n142857@gmail.com, 71223@debbugs.gnu.org
Subject: bug#71223: 30.0.50; stack overflow after very fast opening and closing of frames
Date: Thu, 30 May 2024 07:56:45 +0300 [thread overview]
Message-ID: <86frtzsxrm.fsf@gnu.org> (raw)
In-Reply-To: <jwvfru0tndx.fsf-monnier+emacs@gnu.org> (bug-gnu-emacs@gnu.org)
> Cc: 71223@debbugs.gnu.org
> Date: Wed, 29 May 2024 15:56:17 -0400
> From: Stefan Monnier via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> IIUC this problem is not really new with my code (tho, I guess when the
> process-filters are run in a nested fashion, the various `sit-for` can
> be done in parallel, whereas with my patch they are done sequentially,
> significantly increasing the visible delay when you have many such
> requests).
No, the nested sit-for calls are NOT running in parallel, because
there's just one thread running them all. Only the innermost sit-for
is actually "running", in the sense that its pselect loop in waiting
for input.
So what your change does is replace a depth-first sequence of sit-for
with a kind-of breadth-first sequence. But it's a sequence in either
case.
next prev parent reply other threads:[~2024-05-30 4:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 11:01 bug#71223: 30.0.50; stack overflow after very fast opening and closing of frames Daniel Clemente
2024-05-27 12:23 ` Eli Zaretskii
2024-05-27 12:36 ` Eli Zaretskii
2024-05-27 14:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-27 15:21 ` Eli Zaretskii
2024-05-27 17:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-27 18:15 ` Eli Zaretskii
2024-05-27 18:33 ` Eli Zaretskii
2024-05-29 0:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29 11:48 ` Eli Zaretskii
2024-05-29 20:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-30 5:12 ` Eli Zaretskii
2024-05-30 13:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-30 15:29 ` Eli Zaretskii
2024-05-27 15:21 ` Daniel Clemente
2024-05-27 15:26 ` Eli Zaretskii
2024-05-29 0:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29 10:54 ` Daniel Clemente
2024-05-29 19:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-30 4:56 ` Eli Zaretskii [this message]
2024-05-30 13:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-29 21:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-30 5:19 ` Eli Zaretskii
2024-05-30 16:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-30 16:49 ` Eli Zaretskii
2024-05-30 18:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-30 22:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-31 5:45 ` Eli Zaretskii
2024-05-31 12:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-30 11:22 ` Daniel Clemente
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=86frtzsxrm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71223@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=n142857@gmail.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).