You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So this problem can be spoted if you use the ofLoadURL() function on the update(). After a while you will have a bunch of sockets with the WAIT_CLOSE status and the application will fail. On win10 if you run netstat -an on the command line you will see a bunch of sockets being used there.
After some research I found out the problem may be on this function: ofHttpResponse ofURLFileLoaderImpl::handleRequest(ofHttpRequest request).
This function creates a new instance of HTTPClientSession every time it runs, HTTPClientSession * httpSession = new HTTPClientSession(uri.getHost(), uri.getPort());. And after receiving the info from the link you provided it does not destroy this instance leaving the socket open.
So this problem can be spoted if you use the
ofLoadURL()
function on theupdate()
. After a while you will have a bunch of sockets with the WAIT_CLOSE status and the application will fail. On win10 if you runnetstat -an
on the command line you will see a bunch of sockets being used there.After some research I found out the problem may be on this function:
ofHttpResponse ofURLFileLoaderImpl::handleRequest(ofHttpRequest request)
.This function creates a new instance of HTTPClientSession every time it runs,
HTTPClientSession * httpSession = new HTTPClientSession(uri.getHost(), uri.getPort());
. And after receiving the info from the link you provided it does not destroy this instance leaving the socket open.As I reported on the forum, https://forum.openframeworks.cc/t/repeat-usage-of-ofloadurl-causes-i-o-error-no-buffer-space-available/23747/1 I found out a quick fix (explained there). However, I think it should be better to just use the deconstructor after getting the information from the web link.
I hope this information is enough for you guys to understand the issue 💃
The text was updated successfully, but these errors were encountered: