-
Notifications
You must be signed in to change notification settings - Fork 506
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not allocate socket in Windows #643
Comments
I have not seen it before. Does it work with one input live stream instead of multiple? |
It doesn't happen in one input stream. |
Issue #643. Change-Id: I8adfb9910e1e43294738abb7783a64645a4f42c3
@Jason239 I have updated the code to log the error code on failure. Can you try the latest code? |
The error code 10093 is printed.
and sometimes 10107 is also logged. |
@Jason239 Thanks for testing. 10093 is WSANOTINITIALISED. Right now WSAStartup is called only once for all sockets. Looks like we need to call it once for every sockets. @Korilakkuma You have worked on sockets in Shaka Packager before. Would you be interested in helping us fixing this issue? |
@Jason239 Let us know if it fixes your problem. Thanks. |
When I try to package with multiple input live stream, 'Could not allocate socket' error has continued to occur like this in Windows OS.
Do you know any idea why ?
The command was this.
The text was updated successfully, but these errors were encountered: