multisocketsink: handle client close correctly and EWOULDBLOCK
authorTom Deseyn <tom.deseyn@gmail.com>
Thu, 28 Jan 2016 15:26:47 +0000 (16:26 +0100)
committerTim-Philipp Müller <tim@centricular.com>
Tue, 1 Mar 2016 13:15:38 +0000 (13:15 +0000)
commit8c4d3c6aa9fd0816210ac8b03d958647208bf589
treef4548d196f00ebf870bbe479978d23e0263cb0f4
parentb424712644363288405c911d22b5d028d174db23
multisocketsink: handle client close correctly and EWOULDBLOCK

Fixes 100% cpu usage when client disconnects. Commit 6db2ee56
would just make multisocketsink ignore reads of 0 bytes without
removing the client, so we'd get woken up over and over again
for the client.

Fix the original issue differently by handling the non-fatal error code.

https://bugzilla.gnome.org/show_bug.cgi?id=761257
https://bugzilla.gnome.org/show_bug.cgi?id=743834
gst/tcp/gstmultisocketsink.c