[Bug 724077] New: gstshm: use shutdown() instead of close()

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=724077
  GStreamer | gst-plugins-bad | git

           Summary: gstshm: use shutdown() instead of close()
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: aleix at oblong.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


I've hit a problem with the shared memory elements. 

I have 1 shmsink and 2 shmsrc clients. And sometimes it seems close() is not
enough on the client side. Replacing close() by shutdown() solves the problem.

Unfortunately, I just know (and have only tried actually) how to reproduce it
with one of our apps.

The way I reproduce it is byt creating the clients one after the other (few
seconds difference) and closing them at the same time. If I create both clients
at the same time and close them at the same time, everything works. I know this
explanation sucks and doesn't make much sense, but that's all I know so far.

I don't know why this didn't happen in 0.10, unless something in gstpoll
changed. As far as I can see, shm elements look more or less the same,
specially the closing socket part.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.