all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Kirill Korinsky <kirill@korins.ky>
Cc: 51336@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
	stefankangas@gmail.com
Subject: bug#51336: 29.0.50; Application not responding
Date: Fri, 12 Jan 2024 17:22:54 +0000	[thread overview]
Message-ID: <ZaF1brnFr6PjPTml@idiocy.org> (raw)
In-Reply-To: <2F709323-6F6E-4442-9CB6-EE83F5F4029F@korins.ky>

package emacs
merge 51336 67694
thankyou

On Fri, Jan 12, 2024 at 05:31:49PM +0100, Kirill Korinsky wrote:
> Emacs was frozen (UI) and hasn't response to any command. Before that it had
> happened I'd resized a window.
> 
> I attach and de-attach external screen quite often and it triggers the resize.
> 
> So, when it was frozen I've attached via lldb and get stack traces bellow.
> 
> It is reproducable, not each resize but often enough.
> 
> When it frozen, I need to kill it, otherwise it absolutle useless.
> 
> And this stack trace was obtained from local root d9462e24a967e32d550ee886b5150f0cc78358f6
> 
> (lldb) bt all
> * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
>   * frame #0: 0x00007ff80d07596a libsystem_kernel.dylib`mach_msg_trap + 10
>     frame #1: 0x00007ff80d075cd8 libsystem_kernel.dylib`mach_msg + 56
>     frame #2: 0x00007ff80d17929d CoreFoundation`__CFRunLoopServiceMachPort + 319
>     frame #3: 0x00007ff80d177928 CoreFoundation`__CFRunLoopRun + 1276
>     frame #4: 0x00007ff80d176d6c CoreFoundation`CFRunLoopRunSpecific + 562
>     frame #5: 0x00007ff815e245e6 HIToolbox`RunCurrentEventLoopInMode + 292
>     frame #6: 0x00007ff815e2434a HIToolbox`ReceiveNextEventCommon + 594
>     frame #7: 0x00007ff815e240e5 HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter + 70
>     frame #8: 0x00007ff80fbb1f6d AppKit`_DPSNextEvent + 927
>     frame #9: 0x00007ff80fbb062a AppKit`-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1394
>     frame #10: 0x00007ff80fba2cd9 AppKit`-[NSApplication run] + 586
>     frame #11: 0x0000000104b2449c Emacs`-[EmacsApp run] + 317

OK, I think this is the same as bug#67694, so I'll merge them.

I think we need to revert 6acb3c5b05a7b9fb32a5336e1bb740f527571ae9 as
discussed in that other bug report and re-open bug#65843, if we can.

Unless anyone else has a better idea.
-- 
Alan Third





  parent reply	other threads:[~2024-01-12 17:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 17:13 bug#51336: 29.0.50; Application not responding Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-24 18:34 ` Lars Ingebrigtsen
2021-10-24 19:44   ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-24 19:45     ` Lars Ingebrigtsen
2021-10-24 20:25       ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-25  9:19 ` Alan Third
2022-09-13 14:47   ` Lars Ingebrigtsen
2022-09-13 14:49     ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 15:02       ` Lars Ingebrigtsen
2022-09-13 17:05         ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03  8:46           ` Stefan Kangas
2023-09-03  8:49             ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03  9:03               ` Eli Zaretskii
2023-12-28 17:55                 ` Kirill A. Korinsky
2023-12-28 19:47                   ` Eli Zaretskii
2024-01-12 16:31                     ` Kirill Korinsky
2024-01-12 17:22 ` Alan Third [this message]
2024-01-12 18:14   ` Eli Zaretskii
2024-01-12 18:31     ` Alan Third
2024-01-12 23:53       ` Kirill Korinsky
2024-01-13  6:51       ` Eli Zaretskii
2024-01-13 22:41         ` Kirill Korinsky
2024-01-20  9:23         ` Eli Zaretskii
2024-01-20 13:19           ` Kirill A. Korinsky
2024-01-23 15:33           ` Kirill A. Korinsky

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZaF1brnFr6PjPTml@idiocy.org \
    --to=alan@idiocy.org \
    --cc=51336@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=kirill@korins.ky \
    --cc=stefankangas@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.