Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
December 2016
Description
Connecting socket in nonblocking mode into localhost continued by WSAEnumNetworkEvents doesn't work correctly.
Windows connect() function always return value SOCKET_ERROR, and WSAGetLastError return WSAEWOULDBLOCK, to continue with WSAEnumNetworkEvents configured by WSAAsyncSelect/WSAEventSelect, ReactOS WSA does not.
Simple client/server application is attached to test connecting.
Tested with ReactOS 20161013-r72963 in VirtualBox 5.0.20
(ReactOS seems sometimes (but not always) hang, when trying attached sample)
Attachments
Issue Links
- blocks
-
CORE-10521 Snappy Driver Installer can't download any driver packs.
- Untriaged
- is duplicated by
-
CORE-4099 utorrent download causes softlocks
- Resolved
-
CORE-12191 Issues with opening multiple sites at a time in Pale Moon
- Resolved
-
CORE-15810 μTorrent 2.2.1 (25110): Completely locked GUI because of dialog and menu
- Resolved
-
CORE-18279 µTorrent 2.2.1 stalls
- Resolved
-
CORE-13921 CCleaner 5.1.6 setup from rapps does not draw contents of the dialog that allows deselection of bundled Chrome
- Resolved
-
CORE-14097 Opera 10.50 very slow started
- Resolved
- relates to
-
CORE-17791 Internet Download Manager (IDM) 6.39.2, the mouse movement is extremely slow when downloading something
- Open
-
CORE-16868 "Socket is not connected (#10057 in Disconnect (closesocket))" error when using SUMo / DUMo
- Resolved