Re: UI input unresponsive on macOS

[Gong-Yi Liao 廖宮毅]

I have similar issue on Linux/Gtk3. I am wondering if this is a
threading/concurrency issue.

On Tue, Jan 3, 2017 at 11:49 AM, Alan Third <address@hidden> wrote:
> On Tue, Jan 03, 2017 at 08:59:43AM -0800, Bob Halley wrote:
>>
>> > Can you try the attached patch?
>>
>> It didn’t fix things, but I did find a way to reproduce the problem at will.
>>
>> If start emacs, and then you run
>>
>>     open -a /Applications/Emacs.app whatever_file_here
>
> I didn’t even know you could do that. I wonder if I’ve accidentally
> clobbered some notification or event somewhere. I’ll have to try and
> work out how this works.
>
>> For a file which isn’t open, then the UI becomes unresponsive to
>> input. Typing C-G seems to unstick it eventually, but there can be
>> very long delays (I timed one at 49 seconds) before it beeps and the
>> UI becomes responsive. I’ve seen it spontaneously complete too,
>> again after a long time (at least 30 seconds), but usually it does
>> not complete.
>
> I had some trouble with that sort of thing before. What was happening
> then was that a time‐out in ns_select was being reached before it
> would react. I had thought I’d fixed that particular problem for most
> cases in the last patch, though.
>
>> Sometimes when I “continue” in the debugger it unsticks whatever is
>> stuck, though the file I was trying to open never opens.
>
> One of the bugs I had with an earlier version of this code would go
> away when I put a breakpoint on the relevant function. Debugging can
> be hard. :)
>
> Thanks for your help.
>
> --
> Alan Third
>