[Bug 761257] multisocketsink: doesn't handle client close and EWOULDBLOCK

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=761257

Tim-Philipp Müller <t.i.m at zen.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
Thanks, pushed to master with minor indentation changes. Will pick into 1.6 if
nothing comes up:

commit 8c4d3c6aa9fd0816210ac8b03d958647208bf589
Author: Tom Deseyn <tom.deseyn at gmail.com>
Date:   Thu Jan 28 16:26:47 2016 +0100

    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

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.