I have been using ffdshow tryouts 1.2.4422 in an application deployed onto hundreds of machines. The library is being used to decode XVID encoded AVIs from memory streams.
I am occasionaly catching an unhandled exception in a thread created by FFDshow. Here is the callstack using what debug info I have available:
[Frames below may be incorrect and/or missing, no symbols loaded for ffmpeg.dll]
msacm32.dll!_threadInitialize@4() + 0x1d bytes
msacm32.dll!DllMainCRTStartup@12() + 0x48 bytes
ntdll.dll!LdrpInitialize@12() + 0x94 bytes
kernel32.dll!_WaitForSingleObjectEx@12() + 0xda bytes
kernel32.dll!_WaitForSingleObjectEx@12() + 0xb0 bytes
kernel32.dll!_BaseThreadStart@8() + 0x37 bytes
And the exception itself: Unhandled exception at 0x6d1ca654 in (null)_V18.104.22.168.RLS_20130527_144230.000.dmp: 0xC0000005: Access violation reading location 0x04458000.
I have considering deploying 1.3.4500, but since I can't find any change logs for this version that suggest any bugs have been fixed.
Does this call stack give you any ideas? Is there any way I can get more information from my debug dump (i.e. with the PDB file for ffmpeg.dll?)