From: "Herbert J. Skuhra" <herbert@mailbox.org>
To: emacs-devel@gnu.org
Subject: Re: UI Unresponsive Again on macOS
Date: Mon, 13 Mar 2017 07:23:05 +0100 [thread overview]
Message-ID: <86a88pk852.wl-herbert@mailbox.org> (raw)
In-Reply-To: <20170310145142.GB76673@breton.holly.idiocy.org>
Alan Third skrev:
>
> On Fri, Mar 10, 2017 at 06:40:00AM -0800, Bob Halley wrote:
>> I build from the master branch about once a week. I had no problem
>> with last week's build made early in the morning California time on
>> Sunday the 6th, but the build I just made this morning becomes
>> completely unresponsive after a short time. I don't have an exact
>> recipe to reproduce -- I was just typing, and then stopped for a
>> bit, and then it became completely unresponsive. This happens every
>> time I try to use it.
>>
>> I suspect one or both of these changes:
>>
>> a65236214d9202fb69a6ba5169d4ac1a4bcb0b0d
>> 3bd2e9e975ed29daaf03ca7559e4664aade0674f
>>
>> as they are new since my last working build and seem to be relevant.
>>
>> I obtained backtraces of all the threads. I did two snapshots of
>> thread 1 as it seemed to be spinning a bit.
>
> Thanks for that, Bob. I noticed these hangs too, but I haven’t
> actually managed to catch one in the debugger yet.
>
> Can you please try the attached patch? I’m not at all sure it’ll fix
> it, but it’ll be good to rule it out.
Unfortunately I cannot confirm that this patch fixes the issue on my
system. I still see high cpu usage and hangs when using Gnus (nntp) on
macOS 10.12.4 Beta 5. git bisect showed that
3bd2e9e975ed29daaf03ca7559e4664aade0674f is the culprit.
--
Herbert
next prev parent reply other threads:[~2017-03-13 6:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 14:40 UI Unresponsive Again on macOS Bob Halley
2017-03-10 14:51 ` Alan Third
2017-03-10 15:04 ` Bob Halley
2017-03-13 6:23 ` Herbert J. Skuhra [this message]
2017-03-13 11:42 ` Alan Third
2017-03-14 14:52 ` Alan Third
2017-03-13 18:13 ` Bob Halley
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=86a88pk852.wl-herbert@mailbox.org \
--to=herbert@mailbox.org \
--cc=emacs-devel@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 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).