> On Sep 18, 2016, at 09:58, Keith Packard wrote:
>
> Matthieu Herrb writes:
>
>> this doesn't fix an issue I'm seeing on OpenBSD with xterm not beeing
>> able to start (it makes the X server spin at 100% CPU in
>> WaitForSomething()), while Jeremy's patches do fix the issue for me.
>
> I thi
Matthieu Herrb writes:
> this doesn't fix an issue I'm seeing on OpenBSD with xterm not beeing
> able to start (it makes the X server spin at 100% CPU in
> WaitForSomething()), while Jeremy's patches do fix the issue for me.
I think Jeremy's patch will cause the server to spin while any client i
On Sun, Sep 18, 2016 at 08:42:00AM -0700, Keith Packard wrote:
> Jeremy Huddleston Sequoia writes:
>
> > On encountering an EAGAIN, FlushClient() re-adds the client to the
> > pending list and returns, but FlushClient() doesn't get called again.
> > We would expect it to be called via FlushAllOut
Jeremy Huddleston Sequoia writes:
> On encountering an EAGAIN, FlushClient() re-adds the client to the
> pending list and returns, but FlushClient() doesn't get called again.
> We would expect it to be called via FlushAllOutput() via
> WaitForSomething(), but that only happens when NewOutputPendi
