It fills the log rapidly up to its maximum size of 4 MB with error messages. ![]() They start at a moment when the infinite loop is already going on. Unfortunately the logs (svcdebug.log and the previous svcdebug.bak) don't show what happens before the error occurs for the first time. The (third party) network library used by the DMS (which facilitates using WinSock2) tries to handle the error by closing the connection, but ends up in an infinite loop, that triggers the error again and again, several times per millisecond, which makes the DMS unresponsive. This triggers a WSAENOTSOCK error in Windows. Here is a summary of the results:įor unknown reasons a socket handle, that is important for referencing a network connection, becomes invalid. I've spent some time with investigating the issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |