On Wed, Dec 5, 2018 at 11:11 AM, Eric Williams <ericw...@redhat.com>
wrote:
Some preliminary debugging shows that the web extension still holds
onto the socket/file descriptor used when opening the port in step 1
-- even though the port has been closed. This causes the error in
step 4. If no web extension is created (i.e. step 2 is skipped), then
no error from step 4 happens.
I'm confused and suspect I've misunderstood the scenario. But: why does
WebKit have anything to do with a socket that you create in your own
code?
_______________________________________________
webkit-gtk mailing list
webkit-gtk@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-gtk
