I've downloaded the new TSreader.ax (25251) from the svn; and crashing on recordings are gone for now; installed it on the pre-rc2 disater123 edition.
Sweden
I'm asking since I haven't seen the crash anymore with the SVN TsReader (been using it with the RC1 MP for two weeks).
@tourettes: I've had a similar crash a couple of times. In one occasion I attached VS debugger to see where it crashed and then I saw the real exception which was "buffer overrun".
.NET adds guard cookies on the stack in each call, and if those are corrupt on return it throws the "buffer overrun" exception. However by the time you hit the exception all stack trace is lost and tracking the source of the problem is impossible. Not sure though that this is a TsReader issue.
I'm asking since I haven't seen the crash anymore with the SVN TsReader (been using it with the RC1 MP for two weeks).
I don't know if you missed my post from yesterday but I have now got the crash when TsReader was not even in use. So my conclusion is that this has nothing to do with TsReader but with video playback in general in MP.
@tourettes: I've had a similar crash a couple of times. In one occasion I attached VS debugger to see where it crashed and then I saw the real exception which was "buffer overrun".
.NET adds guard cookies on the stack in each call, and if those are corrupt on return it throws the "buffer overrun" exception. However by the time you hit the exception all stack trace is lost and tracking the source of the problem is impossible. Not sure though that this is a TsReader issue.
I wanted to clarify this a bit more. It is (in theory) impossible to get a buffer overrun in C# (at least not one that would throw this exception and generaly cause unrecoverable errors) because all managed memory allocations are from heap memory not the stack. There are only 3 possible causes:
The fact that the exception occurs in mscorwks.dll does not rule out C++ as that is where the managed/unmanaged marshaling takes place, and it is there that the stack is checked on return to make sure it has not been corrupted by the unmanaged C++ code. So I still think the most probable cause is C++ code (not necessarily TsReader).
- bug in .Net Framework (not impossible but unlikely to have not been spotted so far)
- an "unsafe { }" code block
- C++ code.
Sweden
1) also MKV crash (impossible to be a TsReader bug, unless the tv / recording was on before starting the MKV file)
....
I still would suspect the TsReader since it deals a lot with data and buffer overflow would be pretty easy to cause in such content... but that one MKV related crash is odd...