Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mattkhan]

recently (last week or two at least) I've noticed MC be extremely slow to shutdown, e.g. when there's a new update to install, looking at the logs it seems to be during DLNA shutdown though I'm not aware of any changes in my network (hard to be sure of this of course). The logs are reams of this type

Code: [Select]

85736877: 16252: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (87847 ms)
85736908: 9508: General: VSocketReader::Close: Forced close, will do a RST via SO_LINGER timeout of 0
85736908: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 4216
85736908: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Closed sucessfully
85736908: 5908: Sharing Plugins: CTCPSocketReader::Read: Read failed: Unknown error (10004) (socket: -1)
85736908: 5908: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736908: 5908: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (87876 ms)
85736939: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736939: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736939: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736939: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736939: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736939: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736939: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736939: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736939: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736939: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736939: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736940: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736940: 9508: General: VSocketReader::Close: Forced close, will do a RST via SO_LINGER timeout of 0
85736940: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: shutdown() socket 3292
85736940: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: shutdown() failed, error=10057
85736940: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 3292
85736940: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Closed sucessfully
85736940: 9508: General: VSocketReader::Close: Forced close, will do a RST via SO_LINGER timeout of 0
85736940: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 2928
85736940: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Closed sucessfully
85736940: 9508: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736940: 10496: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736940: 10496: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor
85736940: 10496: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: Close failed. Not open or invalid descriptor

v slow means minutes

if I leave it, it does eventually complete

the issue is that the above blocks the UI, i.e. it freezes, whites out and looks broken

2 things

1) does it really need to cleanly/gracefully shutdown some dlna connections?
2) does it have to block the UI?

[bob]

It is important for the DLNA connections to be shutdown gracefully if possible.
Not doing that will leave remote devices with stray event notifiers pointing to non-existent MC handlers.
That really messes up some devices.
That said even if there is a hung device (or sleeping or hard powered off) device on the network the shutdown process will eventually give up and not in the length you are seeing. More like 10 seconds or so.

There was a change I'm a bit suspicious of just after 33.0.30. Can you revert to that, turn off auto-updates and see if you can still make it happen? If you can would you email a log to me?
bob (at) jriver (dot) com.
Thanks.