[Webkit-unassigned] [Bug 61538] New: [UNIX] SOCK_DGRAM sockets are not notified when the other end closes the connection

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=61538

           Summary: [UNIX] SOCK_DGRAM sockets are not notified when the
                    other end closes the connection
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Keywords: Gtk, Qt
          Severity: Normal
          Priority: P2
         Component: WebKit2
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: cgarcia at igalia.com


A possible solution to this problem is to use SOCK_SEQPACKET instead of SOCK_DGRAM, but it's linux-only, see bug #61287 for more details. So, even if we decice to use SOCK_SEQPACKET when available we still need an implementation when it isn't. The problem of not being notified when the other end closes the connection is that the process might get blocked waiting for a sync reply that will never be received because the other process has closed the connection. This currently happens when the web process sends the DestroyPlugin message to the plugin process and it was the las plugin. In that case the plugin process closes the connection and finishes after a timeout. During that timeout the web process is waiting for the reply to the DestroyPlugin message, and it doesn't wake uo until the plugin process really dies.

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