Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 915084" data-attributes="member: 82144">It is technical - a little difficult to explain.You might think of a deadlock like two children fighting over a toy. The toy has to be shared for optimal happiness; when one child refuses to give up the toy, bad things happen. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />&nbsp;TsWriter (responsible for TV Server grunt work like writing recording and timeshifting files to disk, decoding the service information in the stream, grabbing and decoding EPG etc.) has &quot;toys&quot; called locks. These are used to ensure that TV Server keeps functioning correctly when you're recording/timeshifting multiple channels with a single tuner. Sometimes, certain sequences of events or bugs or corruptions in the stream seem to be able to cause TsWriter to not release these locks when it should. Like a child that doesn't want to share their toys with another child, this causes major problems for the TV library and wider TV service. TsWriter becomes unresponsive, and this causes all the other symptoms (eg. requiring task manager to kill TVService.exe, live TV not starting, recordings not working).&nbsp;Some people have reported success by unticking &quot;enable CRC check&quot; in the DVB EPG grabber section of TV Server configuration. Other than that, there is nothing I can suggest except trying the patch or not using the EPG grabber at all.&nbsp;This deadlock has been a very frustrating issue for us as we haven't been able to find a way to consistently reproduce it. We would *really* appreciate it if you could help us in this regard by testing the patch and reporting your results. If this is happening to you on a regular basis - even hourly - then it also might help if we could get a sample of the full stream from your TV provider. The tv.log and TsWriter***.log are also critical pieces of information.&nbsp;At this point I'm not able to imagine how the N/A tuner issue could be connected to the deadlock. I'll keep considering...&nbsp;mm</blockquote>

[QUOTE="mm1352000, post: 915084, member: 82144"] It is technical - a little difficult to explain. You might think of a deadlock like two children fighting over a toy. The toy has to be shared for optimal happiness; when one child refuses to give up the toy, bad things happen. ;) TsWriter (responsible for TV Server grunt work like writing recording and timeshifting files to disk, decoding the service information in the stream, grabbing and decoding EPG etc.) has "toys" called locks. These are used to ensure that TV Server keeps functioning correctly when you're recording/timeshifting multiple channels with a single tuner. Sometimes, certain sequences of events or bugs or corruptions in the stream seem to be able to cause TsWriter to not release these locks when it should. Like a child that doesn't want to share their toys with another child, this causes major problems for the TV library and wider TV service. TsWriter becomes unresponsive, and this causes all the other symptoms (eg. requiring task manager to kill TVService.exe, live TV not starting, recordings not working). Some people have reported success by unticking "enable CRC check" in the DVB EPG grabber section of TV Server configuration. Other than that, there is nothing I can suggest except trying the patch or not using the EPG grabber at all. This deadlock has been a very frustrating issue for us as we haven't been able to find a way to consistently reproduce it. We would *really* appreciate it if you could help us in this regard by testing the patch and reporting your results. If this is happening to you on a regular basis - even hourly - then it also might help if we could get a sample of the full stream from your TV provider. The tv.log and TsWriter***.log are also critical pieces of information. At this point I'm not able to imagine how the N/A tuner issue could be connected to the deadlock. I'll keep considering... mm [/QUOTE]

Verification