From: David Reitter <david.reitter@gmail.com>
To: 18848@debbugs.gnu.org
Subject: bug#18848: hang is in [EmacsApp run] (24.4.51; Hang after toolbar use)
Date: Tue, 28 Oct 2014 23:51:21 -0400 [thread overview]
Message-ID: <A25B6D39-7BD2-4D72-ADE3-E3085E55A8AC@gmail.com> (raw)
In-Reply-To: <928A1DBA-26EA-432B-A336-82292664FD21@gmail.com>
The hang occurs in the “run” method (of EmacsApp), specifically this function call:
NSEvent *event =
[self nextEventMatchingMask:NSAnyEventMask
untilDate:[NSDate distantFuture]
inMode:NSDefaultRunLoopMode
dequeue:YES];
does not appear to return.
I have tried using [NSDate dateWithTimeIntervalSinceNow:2], but that doesn’t work either.
> On Oct 27, 2014, at 8:40 PM, David Reitter <david.reitter@gmail.com> wrote:
>
> interrupt_input_blocked is often 0 when the hang occurs, but I noticed some strange conditions when interrupting a non-hanging Emacs:
>
> (lldb) print interrupt_input_blocked
> (int) $9 = -1
>
> or interrupt_input_blocked has a nonsensical value:
>
> (lldb) print interrupt_input_blocked
> (int) $3 = 1157628088
>
> I have tried placing a warning in unblock_input() to notify of negative values for interrupt_input_blocked, but that didn’t lead to anything in conjunction with the toolbar double-click.
>
> So maybe this is all a red herring.
next prev parent reply other threads:[~2014-10-29 3:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 1:57 bug#18848: 24.4.51; Hang after toolbar use David Reitter
[not found] ` <handler.18848.B.141437508615391.ack@debbugs.gnu.org>
2014-10-28 0:40 ` bug#18848: Acknowledgement (24.4.51; Hang after toolbar use) David Reitter
2014-10-29 3:51 ` David Reitter [this message]
2014-10-29 13:47 ` bug#18848: hang is in [EmacsApp run] " David Reitter
2014-11-08 16:34 ` Jan D.
2014-11-08 17:06 ` David Reitter
2014-11-08 17:19 ` Jan D.
2014-11-08 18:03 ` David Reitter
2014-11-15 18:24 ` Jan D.
2014-11-07 18:24 ` bug#18848: Yosemite problem David Reitter
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=A25B6D39-7BD2-4D72-ADE3-E3085E55A8AC@gmail.com \
--to=david.reitter@gmail.com \
--cc=18848@debbugs.gnu.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 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.