Reply to thread

Message

<blockquote data-quote="Owlsroost" data-source="post: 1002446" data-attributes="member: 83973">It feels like the graph is hanging (and this ties in with having to kill the whole process to recover from it) - I've had this happen often enough when doing dev work on TsReader and dshowhelper....<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /> . The deadlock might not be just inside TsWriter - there are presumably other filters in the graph which are feeding TsWriter with data, and also receiving Pause(), Stop(), Run() commands from the filtergraph manager, so it could be timing issue involving more than one filter.&nbsp;One question is - do we actually need the locking in Pause(), Stop() etc - is it doing anything useful inside TsWriter ? (or do we need to hold the lock for the whole time in Pause(), Stop() etc ?)</blockquote>

[QUOTE="Owlsroost, post: 1002446, member: 83973"] It feels like the graph is hanging (and this ties in with having to kill the whole process to recover from it) - I've had this happen often enough when doing dev work on TsReader and dshowhelper....;) . The deadlock might not be just inside TsWriter - there are presumably other filters in the graph which are feeding TsWriter with data, and also receiving Pause(), Stop(), Run() commands from the filtergraph manager, so it could be timing issue involving more than one filter. One question is - do we actually need the locking in Pause(), Stop() etc - is it doing anything useful inside TsWriter ? (or do we need to hold the lock for the whole time in Pause(), Stop() etc ?) [/QUOTE]

Verification