This project is read-only.

1.5.9 - 1.5.11 Lost communication with worker process: System.TimeoutException


I have been slowly ripping a dvd set and I have had an intermittent problem that has persisted through several beta releases. Each disc had 3 episodes on it which I queue up using 'add multiple titles to queue...' The first episode always encodes succesfully but about half or one-third of the time the 2 other episodes will fail with the error log below. I am using the latest Vidcoder and the latest AnyDVD HD as they're released.
## VidCoder (x64)
# Starting job 2/3
#   Path: N:\
#   Title: 3
#   Range: All
# Worker ready: Service state is Opened on pipe VidCoderWorker.dff1ac6a-be14-4208-b41f-4e7f04e09d14
# Connecting to process 2140 on pipe VidCoderWorker.dff1ac6a-be14-4208-b41f-4e7f04e09d14
[10:45:12] hb_init: starting libhb thread
[10:45:12] CPU: Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz
[10:45:12]  - logical processor count: 8
# Lost communication with worker process: System.TimeoutException: This request operation sent to net.pipe://localhost/VidCoderWorker.dff1ac6a-be14-4208-b41f-4e7f04e09d14 did not receive a reply within the configured timeout (00:00:10).  The time allotted to this operation may have been a portion of a longer timeout.  This may be because the service is still processing the operation or because the service was unable to send a reply message.  Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

Server stack trace: 
   at System.ServiceModel.Dispatcher.DuplexChannelBinder.SyncDuplexRequest.WaitForReply(TimeSpan timeout)
   at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at VidCoderWorker.IHandBrakeEncoder.StartEncode(EncodeJob job, Boolean preview, Int32 previewNumber, Int32 previewSeconds, Double overallSelectedLengthSeconds, Int32 verbosity, Int32 previewCount, Boolean useDvdNav)
   at VidCoder.RemoteEncodeProxy.<>c__DisplayClass7.<>c__DisplayClassa.<StartEncode>b__5() in d:\docs\projects\VidCoder\VidCoder\Services\EncodeProxy\RemoteEncodeProxy.cs:line 118
   at VidCoder.RemoteEncodeProxy.ExecuteProxyOperation(Action action) in d:\docs\projects\VidCoder\VidCoder\Services\EncodeProxy\RemoteEncodeProxy.cs:line 357
# Encode failed.
# Job completed (Elapsed Time: 10s)


RandomEngy wrote Nov 7, 2013 at 4:39 PM

Hmm. Haven't seen this problem in a while. What happens when you disable Options -> Advanced -> Use Worker Process to Encode ?

starkebn wrote Nov 10, 2013 at 9:30 PM

I was able to encode 9 separate files without a problem when I turned off the worker thread option. Only a small sample size but it seems better