On 12/5/18 1:14 PM, Michael Catanzaro wrote:
On Wed, Dec 5, 2018 at 11:11 AM, Eric Williams <[email protected]> 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?
This is kind of what I'm trying to get at: is it possible that WebKit
gets a copy of all open sockets somehow when creating an extension? If
this is completely outside the realm of possibility then I'll
investigate further.
Eric
_______________________________________________
webkit-gtk mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-gtk
