On Mon, 2012-01-02 at 14:23 +0200, Tanu Kaskinen wrote: > The reason why I thought adding PA_IO_EVENT_INVALID would not be useful > was that it wouldn't solve my immediate problem any better than reusing > ERROR, and actually it would not solve the problem at all without > further debugging: I would need to find out what IO event exactly is > causing the 100% cpu use and then add a check for INVALID to that code. > I still don't know what code that is - I suspected GStreamer, but it > seems that pulsesink doesn't create any IO events of its own. There were > two fds involved. The other one should be the unix socket that is used > to communicate with the daemon. I think that code can't enter a busy > loop even if POLLNVAL occurs. I don't know what the other fd is - I'll > need to investigate this more. Update: the 100% cpu use bug was reproduced again today, so apparently my patch didn't help with that after all. -- Tanu
