From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: Po Lu <luangruo@yahoo.com>, 45658@debbugs.gnu.org
Subject: bug#45658: Infinite loop in run loop on macOS
Date: Wed, 20 Oct 2021 21:39:10 +0100 [thread overview]
Message-ID: <ECD266BE-DDAD-4670-98B9-B0A857008180@gmail.com> (raw)
In-Reply-To: <YXB7DPXLrjdoaBT4@idiocy.org>
I haven't seen this for quite some time now, but then I've switched to emacs 28 some time ago too. I'm not sure if it's still a problem on emacs 27.
> On 20 Oct 2021, at 9:24 pm, Alan Third <alan@idiocy.org> wrote:
> On Wed, Oct 20, 2021 at 10:02:23AM +0800, Po Lu wrote:
>> Alan Third <alan@idiocy.org> writes:
>>
>>> ns_send_appdefined somewhere. Can you switch to the thread that's
>>> running fd_handler and see what it's doing? There are only two
>>> branches, so it should be easy to work out which one is in use.
>>
>>>> frame #8: 0x00007fff2d14c039 AppKit`_DPSNextEvent + 883
>>>> frame #9: 0x00007fff2d14a880 AppKit`-[NSApplication(NSEvent)
>>>> _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
>>>> frame #10: 0x00007fff2d13c58e AppKit`-[NSApplication run] + 658
>>>> frame #11: 0x000000010036c5fa Emacs`-[EmacsApp
>>>> run](self=0x000000010525e180, _cmd="run") at nsterm.m:5602:9
>>>> frame #12: 0x000000010036a8eb Emacs`ns_select(nfds=30,
>>>> readfds=0x00007ffeefbfd1f0, writefds=0x00007ffeefbfd170,
>>>> exceptfds=0x0000000000000000, timeout=0x00007ffeefbfd148,
>>>> sigmask=0x0000000000000000) at nsterm.m:4690:3
>>
>> Does it also make sense for this to occur on GNUstep? I have just seen
>> a very similar bug there, but I lost the backtrace :(
>
> It doesn't make any sense to me for it to happen anywhere. ;)
>
> If it happens on macOS I don't see why it shouldn't happen on GNUstep,
> unless it's a bug in Cocoa and not in GNUstep. I wasn't able to
> replicate the crash and I don't have any real clue what was causing it
> for Jimmy.
> --
> Alan Third
next prev parent reply other threads:[~2021-10-20 20:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e73a23d1-46b8-1542-5996-ca1afb5b0d30@gmail.com>
[not found] ` <X+78YNyHEa36fYsp@breton.holly.idiocy.org>
[not found] ` <CAKDRQS5eF0S2nk70mcW20yz_A8J36M=qtMwsTaV_wKWgTUZOwQ@mail.gmail.com>
[not found] ` <X/NQ2mjwBp0+Ex+c@breton.holly.idiocy.org>
[not found] ` <CAKDRQS40rKnNmTqbJM97OETfCKnz=5EvUNf1pDZiEWx-iD6+Yw@mail.gmail.com>
2021-01-06 18:53 ` bug#45658: Infinite loop in run loop on macOS Alan Third
2021-01-09 23:21 ` Jimmy Yuen Ho Wong
2021-01-09 23:33 ` Jimmy Yuen Ho Wong
2021-01-10 0:01 ` Alan Third
2021-01-10 0:46 ` Jimmy Yuen Ho Wong
2021-01-10 10:28 ` Alan Third
2021-01-14 9:52 ` Jimmy Yuen Ho Wong
2021-10-20 2:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-20 20:24 ` Alan Third
2021-10-20 20:39 ` Jimmy Yuen Ho Wong [this message]
2022-01-31 17:19 ` Lars Ingebrigtsen
2022-03-01 15:45 ` Lars Ingebrigtsen
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=ECD266BE-DDAD-4670-98B9-B0A857008180@gmail.com \
--to=wyuenho@gmail.com \
--cc=45658@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=luangruo@yahoo.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).